Project Number Date
test_Tails_ISO_stable 5500 06 Mar 2025, 20:33

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 18:55.755 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:58.910
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.499
When I start Tails from USB drive "old" with network unplugged 1:23.943
Then the boot device has safe access rights 3.159
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:330 6.958
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.078
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login 1:23.911
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 30.546
And I take note of which tps features are available 1.963
Then a Tails persistence partition exists on USB drive "old" 0.824
And I shutdown Tails and wait for the computer to power off 8.365
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.888
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.091
Then Tails is running from USB drive "old" 0.583
And all tps features are active 1.900
When I write some files expected to persist 1.843
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 3.161
And I take note of which tps features are available 0.530
And I shutdown Tails and wait for the computer to power off 6.599
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.320
After features/support/hooks.rb:330 0.114
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.857
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 10.153
And I log in to a new session 19.219
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.878
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.691
Then the running Tails is installed on USB drive "to_upgrade" 24.094
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 2.434
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.602
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.496
Then all tps features from the old Tails version are active 1.744
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.512
And the expected persistent files created with the old Tails version are present in the filesystem 1.767
And all persistent directories from the old Tails version have safe access rights 2.566
After features/support/hooks.rb:330 1.285
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:33.163
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 with a persistent partition enabled and logged in 11.788
And no SquashFS delta is installed 0.172
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.643
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.062
And Tor is ready 21.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.873
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.294
Given I shutdown Tails and wait for the computer to power off 11.163
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.490
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.360
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.371
# 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.365
When the network is plugged 0.072
And Tor is ready 17.985
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.194
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.694
Given I shutdown Tails and wait for the computer to power off 4.435
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.485
Then Tails is running version 6.3~testoverlayfs 0.039
And all tps features are active 2.281
And the file system changes introduced in version 6.3~testoverlayfs are present 0.546
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.064
And Tor is ready 20.623
Then the Upgrader considers the system as up-to-date 0.360
# 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 15.725
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.045
After features/support/hooks.rb:330 0.685
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.253
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 with a persistent partition enabled and logged in 9.852
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.496
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 19.493
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.136
After features/support/hooks.rb:330 0.738
After features/support/hooks.rb:100 0.000