Project Number Date
test_Tails_ISO_stable-flatpak 12 10 Sep 2026, 07:36

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 11:27.482 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
1:8.450
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.036
When I start Tails from USB drive "old" with network unplugged 52.032
Then the boot device has safe access rights 1.675
And Tails is running from USB drive "old" 0.182
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.167
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:339 1.673
After features/support/hooks.rb:108 0.006
Tags: @product
1:21.925
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 47.938
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 24.422
And I take note of which tps features are available 6.125
Then a Tails persistence partition exists on USB drive "old" 0.473
And I shutdown Tails and wait for the computer to power off 2.627
After features/support/hooks.rb:339 0.366
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.666
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.802
Then Tails is running from USB drive "old" 0.202
And all tps features are active 6.999
When I write some files expected to persist 1.342
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.315
And all persistent directories from the old Tails version have safe access rights 1.916
And I take note of which tps features are available 6.578
And I shutdown Tails and wait for the computer to power off 3.987
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.279
After features/support/hooks.rb:339 0.134
After features/support/hooks.rb:108 0.007
Tags: @product
2:12.157
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.354
And I log in to a new session 11.207
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.683
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.192
Then the running Tails is installed on USB drive "to_upgrade" 18.253
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 0.786
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.605
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.792
Then all tps features from the old Tails version are active 1.118
And Tails is running from USB drive "to_upgrade" 0.203
And the boot device has safe access rights 2.207
And the expected persistent files created with the old Tails version are present in the filesystem 1.250
And all persistent directories from the old Tails version have safe access rights 1.939
After features/support/hooks.rb:339 0.670
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
3:37.153
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.386
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.169
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.339
When the network is plugged 0.036
And Tor is ready 11.959
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.116
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.069
Given I shutdown Tails and wait for the computer to power off 6.634
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.815
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.631
And the file system changes introduced in version 6.2~testoverlayfs are present 0.171
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.092
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.147
When the network is plugged 0.034
And Tor is ready 10.765
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.047
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.028
Given I shutdown Tails and wait for the computer to power off 2.564
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.376
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.099
And the file system changes introduced in version 6.3~testoverlayfs are present 0.347
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.167
When the network is plugged 0.036
And Tor is ready 10.483
Then the Upgrader considers the system as up-to-date 0.093
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 3.687
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.332
After features/support/hooks.rb:339 0.718
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.521
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.326
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 8.526
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.255
After features/support/hooks.rb:339 0.711
After features/support/hooks.rb:108 0.000