Project Number Date
test_Tails_ISO_test-suite-options 12 28 Jun 2025, 21:19

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 27:36.012 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:4.107
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.240
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 42.160
When I start Tails from USB drive "old" with network unplugged 2:15.669
Then the boot device has safe access rights 3.445
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.092
And process "udev-watchdog" is running 0.155
And udev-watchdog is monitoring the correct device 0.527
And I unplug USB drive "old" 0.311
After features/support/hooks.rb:330 3.686
After features/support/hooks.rb:100 0.010
Tags: @product
3:13.681
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 2.082
And I start Tails from USB drive "old" with network unplugged and I login 2:10.836
Then Tails is running from USB drive "old" 0.458
And I create a persistent partition 43.851
And I take note of which tps features are available 2.618
Then a Tails persistence partition exists on USB drive "old" 3.399
And I shutdown Tails and wait for the computer to power off 10.435
After features/support/hooks.rb:330 0.216
After features/support/hooks.rb:100 0.011
Tags: @product
4:25.059
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.033
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:23.254
Then Tails is running from USB drive "old" 0.732
And all tps features are active 2.939
When I write some files expected to persist 6.926
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.362
And all persistence configuration files have safe access rights 0.750
And all persistent directories from the old Tails version have safe access rights 3.262
And I take note of which tps features are available 0.514
And I shutdown Tails and wait for the computer to power off 5.082
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 40.963
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.010
Tags: @product
3:29.014
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 17.550
And I log in to a new session 27.116
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.455
And I plug USB drive "to_upgrade" 2.512
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.759
Then the running Tails is installed on USB drive "to_upgrade" 43.885
And I unplug USB drive "to_upgrade" 0.493
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:330 3.721
After features/support/hooks.rb:100 0.000
Tags: @product
3:6.562
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.232
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:49.663
Then all tps features from the old Tails version are active 5.754
And Tails is running from USB drive "to_upgrade" 0.873
And the boot device has safe access rights 4.682
And the expected persistent files created with the old Tails version are present in the filesystem 1.665
And all persistent directories from the old Tails version have safe access rights 3.691
After features/support/hooks.rb:330 0.871
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
9:19.628
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 20.623
And no SquashFS delta is installed 1.327
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.370
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.448
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.875
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.318
When the network is plugged 0.135
And Tor is ready 23.193
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.828
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.945
Given I shutdown Tails and wait for the computer to power off 13.046
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:52.107
Then Tails is running version 6.2~testoverlayfs 0.228
And all tps features are active 6.331
And the file system changes introduced in version 6.2~testoverlayfs are present 0.481
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.421
# 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.271
When the network is plugged 0.076
And Tor is ready 25.202
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.744
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.840
Given I shutdown Tails and wait for the computer to power off 9.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:52.353
Then Tails is running version 6.3~testoverlayfs 0.114
And all tps features are active 5.665
And the file system changes introduced in version 6.3~testoverlayfs are present 1.615
And only the 6.3~testoverlayfs SquashFS delta is installed 0.262
# 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.448
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.956
When the network is plugged 0.170
And Tor is ready 24.985
Then the Upgrader considers the system as up-to-date 0.345
# 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 22.317
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.103
After features/support/hooks.rb:330 0.958
After features/support/hooks.rb:100 0.456
Tags: @product @automatic_upgrade
57.958
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.138
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the signing key used by the Upgrader is outdated 0.135
But a current signing key is available on our website 0.000
When the network is plugged 0.241
And Tor is ready 29.995
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.892
After features/support/hooks.rb:330 0.798
After features/support/hooks.rb:100 0.000