Project Number Date
test_Tails_ISO_codespell 12 26 Jun 2025, 11:15

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 28:11.381 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
2:57.814
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.072
And I write an old version of the Tails USB image to disk "old" 39.458
When I start Tails from USB drive "old" with network unplugged 2:6.173
Then the boot device has safe access rights 9.544
And Tails is running from USB drive "old" 0.405
And there is no persistence partition on USB drive "old" 0.123
And process "udev-watchdog" is running 0.182
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:330 1.701
After features/support/hooks.rb:100 0.011
Tags: @product
2:55.539
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:54.061
Then Tails is running from USB drive "old" 1.100
And I create a persistent partition 43.602
And I take note of which tps features are available 2.539
Then a Tails persistence partition exists on USB drive "old" 1.581
And I shutdown Tails and wait for the computer to power off 12.464
After features/support/hooks.rb:330 0.462
After features/support/hooks.rb:100 0.034
Tags: @product
4:9.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.278
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:4.350
Then Tails is running from USB drive "old" 1.621
And all tps features are active 5.560
When I write some files expected to persist 5.672
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.474
And all persistence configuration files have safe access rights 0.710
And all persistent directories from the old Tails version have safe access rights 3.582
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 7.023
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 40.227
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.009
Tags: @product
3:32.282
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.578
And I log in to a new session 23.603
And I clone USB drive "old" to a new USB drive "to_upgrade" 8.321
And I plug USB drive "to_upgrade" 3.392
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:4.145
Then the running Tails is installed on USB drive "to_upgrade" 35.757
And I unplug USB drive "to_upgrade" 0.257
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:330 7.392
After features/support/hooks.rb:100 0.000
Tags: @product
3:40.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:25.360
Then all tps features from the old Tails version are active 4.427
And Tails is running from USB drive "to_upgrade" 0.460
And the boot device has safe access rights 4.188
And the expected persistent files created with the old Tails version are present in the filesystem 1.685
And all persistent directories from the old Tails version have safe access rights 3.710
After features/support/hooks.rb:330 0.662
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
9:47.018
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 21.411
And no SquashFS delta is installed 1.796
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.440
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.151
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.023
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.197
When the network is plugged 0.107
And Tor is ready 31.414
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.268
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 20.674
Given I shutdown Tails and wait for the computer to power off 15.528
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:50.147
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 6.361
And the file system changes introduced in version 6.2~testoverlayfs are present 0.774
And only the 6.2~testoverlayfs SquashFS delta is installed 0.134
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.568
# 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.700
When the network is plugged 0.102
And Tor is ready 22.999
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 14.383
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.091
Given I shutdown Tails and wait for the computer to power off 8.958
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:53.444
Then Tails is running version 6.3~testoverlayfs 0.067
And all tps features are active 7.653
And the file system changes introduced in version 6.3~testoverlayfs are present 1.666
And only the 6.3~testoverlayfs SquashFS delta is installed 0.107
# 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.406
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.619
When the network is plugged 0.096
And Tor is ready 28.996
Then the Upgrader considers the system as up-to-date 0.641
# 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 23.715
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.345
After features/support/hooks.rb:330 1.142
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
1:8.703
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.864
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.284
And the signing key used by the Upgrader is outdated 0.128
But a current signing key is available on our website 0.000
When the network is plugged 0.522
And Tor is ready 52.594
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.880
After features/support/hooks.rb:330 1.163
After features/support/hooks.rb:100 0.000