Project Number Date
test_Tails_ISO_21565-flatpak-safe 58 28 Sep 2026, 22:14

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 10:55.458 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:16.051
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 12.986
When I start Tails from USB drive "old" with network unplugged 59.356
Then the boot device has safe access rights 2.007
And Tails is running from USB drive "old" 0.186
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 1.527
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.351
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 47.210
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 22.878
And I take note of which tps features are available 5.886
Then a Tails persistence partition exists on USB drive "old" 0.525
And I shutdown Tails and wait for the computer to power off 2.538
After features/support/hooks.rb:339 0.499
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.065
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.626
Then Tails is running from USB drive "old" 0.196
And all tps features are active 6.786
When I write some files expected to persist 1.017
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 1.532
And I take note of which tps features are available 5.739
And I shutdown Tails and wait for the computer to power off 2.519
# 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.081
After features/support/hooks.rb:339 0.238
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.916
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 without a persistent partition and stopped at Tails Greeter's login screen 8.332
And I log in to a new session 10.750
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.698
And I plug USB drive "to_upgrade" 2.258
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.228
Then the running Tails is installed on USB drive "to_upgrade" 17.415
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.862
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.635
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.118
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.711
Then all tps features from the old Tails version are active 1.104
And Tails is running from USB drive "to_upgrade" 0.188
And the boot device has safe access rights 1.955
And the expected persistent files created with the old Tails version are present in the filesystem 1.076
And all persistent directories from the old Tails version have safe access rights 1.481
After features/support/hooks.rb:339 0.562
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:17.983
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.184
And no SquashFS delta is installed 0.065
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.028
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.275
When the network is plugged 0.038
And Tor is ready 11.596
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.444
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.308
Given I shutdown Tails and wait for the computer to power off 5.230
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.089
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.358
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.094
# 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.182
When the network is plugged 0.047
And Tor is ready 10.047
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.312
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.482
Given I shutdown Tails and wait for the computer to power off 2.589
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.900
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.815
And the file system changes introduced in version 6.3~testoverlayfs are present 0.224
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.083
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.045
And Tor is ready 10.019
Then the Upgrader considers the system as up-to-date 0.088
# 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.153
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.319
After features/support/hooks.rb:339 0.903
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
17.455
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 7.728
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 7.958
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.426
After features/support/hooks.rb:339 0.732
After features/support/hooks.rb:108 0.000