Project Number Date
test_Tails_ISO_stable 5558 06 Apr 2025, 12:42

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:50.909 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.628
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.428
When I start Tails from USB drive "old" with network unplugged 1:24.024
Then the boot device has safe access rights 2.959
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:330 3.674
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.147
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:23.121
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 31.633
And I take note of which tps features are available 1.692
Then a Tails persistence partition exists on USB drive "old" 0.745
And I shutdown Tails and wait for the computer to power off 8.466
After features/support/hooks.rb:330 0.167
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.942
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.896
Then Tails is running from USB drive "old" 0.378
And all tps features are active 1.828
When I write some files expected to persist 1.760
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
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.248
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.691
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.829
After features/support/hooks.rb:330 0.114
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.425
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 9.505
And I log in to a new session 17.838
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.589
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.837
Then the running Tails is installed on USB drive "to_upgrade" 25.833
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:330 1.717
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.102
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.812
Then all tps features from the old Tails version are active 1.537
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.372
And the expected persistent files created with the old Tails version are present in the filesystem 1.474
And all persistent directories from the old Tails version have safe access rights 2.391
After features/support/hooks.rb:330 1.248
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:22.469
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.581
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.394
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.073
And Tor is ready 20.221
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.553
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.262
Given I shutdown Tails and wait for the computer to power off 8.647
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.895
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.036
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.270
# 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.242
When the network is plugged 0.065
And Tor is ready 18.026
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.449
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.219
Given I shutdown Tails and wait for the computer to power off 4.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.033
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.034
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.070
And Tor is ready 17.738
Then the Upgrader considers the system as up-to-date 0.405
# 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 14.700
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.863
After features/support/hooks.rb:330 0.801
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
57.193
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.931
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.650
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.114
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 45.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.581
After features/support/hooks.rb:330 0.688
After features/support/hooks.rb:100 0.000