Project Number Date
test_Tails_ISO_stable 5991 08 Dec 2025, 19:43

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 17:48.486 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
3:13.375
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 58.535
When I start Tails from USB drive "old" with network unplugged 2:3.415
Then the boot device has safe access rights 4.709
And Tails is running from USB drive "old" 4.799
And there is no persistence partition on USB drive "old" 0.200
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:331 5.627
After features/support/hooks.rb:100 0.018
Tags: @product
2:14.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:29.797
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 28.690
And I take note of which tps features are available 4.501
Then a Tails persistence partition exists on USB drive "old" 2.304
And I shutdown Tails and wait for the computer to power off 8.431
After features/support/hooks.rb:331 0.661
After features/support/hooks.rb:100 0.008
Tags: @product
2:23.791
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.803
Then Tails is running from USB drive "old" 0.725
And all tps features are active 11.855
When I write some files expected to persist 1.997
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.280
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.442
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 8.844
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.777
After features/support/hooks.rb:331 0.296
After features/support/hooks.rb:100 0.009
Tags: @product
3:14.651
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.627
And I log in to a new session 17.558
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.787
And I plug USB drive "to_upgrade" 2.649
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:18.316
Then the running Tails is installed on USB drive "to_upgrade" 20.318
And I unplug USB drive "to_upgrade" 0.181
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:331 3.939
After features/support/hooks.rb:100 0.000
Tags: @product
1:25.330
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.867
Then all tps features from the old Tails version are active 1.451
And Tails is running from USB drive "to_upgrade" 0.281
And the boot device has safe access rights 2.890
And the expected persistent files created with the old Tails version are present in the filesystem 1.356
And all persistent directories from the old Tails version have safe access rights 2.311
After features/support/hooks.rb:331 0.607
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:51.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.206
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.501
When the network is plugged 0.091
And Tor is ready 14.007
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.995
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.266
Given I shutdown Tails and wait for the computer to power off 11.492
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:27.146
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.039
And the file system changes introduced in version 6.2~testoverlayfs are present 0.252
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.229
When the network is plugged 0.058
And Tor is ready 31.218
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.644
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.560
Given I shutdown Tails and wait for the computer to power off 7.874
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.977
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.698
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.168
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.054
And Tor is ready 12.755
Then the Upgrader considers the system as up-to-date 0.151
# 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 5.892
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.485
After features/support/hooks.rb:331 1.010
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
25.637
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.735
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 11.544
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.861
After features/support/hooks.rb:331 0.693
After features/support/hooks.rb:100 0.000