Project Number Date
test_Tails_ISO_stable 5581 17 Apr 2025, 22:25

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 21:20.484 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:17.994
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 30.704
When I start Tails from USB drive "old" with network unplugged 1:41.560
Then the boot device has safe access rights 3.325
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 7.102
After features/support/hooks.rb:100 0.012
Tags: @product
2:16.446
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:30.858
Then Tails is running from USB drive "old" 0.483
And I create a persistent partition 32.389
And I take note of which tps features are available 2.657
Then a Tails persistence partition exists on USB drive "old" 0.852
And I shutdown Tails and wait for the computer to power off 8.992
After features/support/hooks.rb:330 0.185
After features/support/hooks.rb:100 0.011
Tags: @product
3:22.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.060
Then Tails is running from USB drive "old" 1.300
And all tps features are active 5.995
When I write some files expected to persist 2.934
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.308
And all persistence configuration files have safe access rights 0.448
And all persistent directories from the old Tails version have safe access rights 2.851
And I take note of which tps features are available 2.954
And I shutdown Tails and wait for the computer to power off 6.511
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.171
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.012
Tags: @product
2:43.010
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.330
And I log in to a new session 21.280
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.722
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.887
Then the running Tails is installed on USB drive "to_upgrade" 28.866
And I unplug USB drive "to_upgrade" 0.277
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 1.151
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.965
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.078
Then all tps features from the old Tails version are active 1.972
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.727
And the expected persistent files created with the old Tails version are present in the filesystem 1.590
And all persistent directories from the old Tails version have safe access rights 3.047
After features/support/hooks.rb:330 1.351
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:35.614
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.108
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.539
When the network is plugged 0.065
And Tor is ready 26.432
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.876
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.730
Given I shutdown Tails and wait for the computer to power off 9.147
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:52.923
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.942
And the file system changes introduced in version 6.2~testoverlayfs are present 0.411
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.379
# 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.316
When the network is plugged 0.072
And Tor is ready 21.990
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.910
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.166
Given I shutdown Tails and wait for the computer to power off 6.781
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.765
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.021
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.395
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.331
When the network is plugged 0.066
And Tor is ready 16.307
Then the Upgrader considers the system as up-to-date 0.312
# 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.669
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.462
After features/support/hooks.rb:330 0.780
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
40.688
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.452
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 21.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.986
After features/support/hooks.rb:330 0.859
After features/support/hooks.rb:100 0.000