Project Number Date
test_Tails_ISO_stable 4969 24 Jul 2024, 12:12

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:50.299 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:29.852
Before features/support/hooks.rb:269 0.007
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 31.095
When I start Tails from USB drive "old" with network unplugged 1:53.224
Then the boot device has safe access rights 3.040
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.134
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:326 8.064
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.944
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:59.509
Then Tails is running from USB drive "old" 0.397
And I create a persistent partition 32.176
And I take note of which tps features are available 1.919
Then a Tails persistence partition exists on USB drive "old" 1.049
And I shutdown Tails and wait for the computer to power off 8.685
After features/support/hooks.rb:326 0.236
After features/support/hooks.rb:100 0.011
Tags: @product
3:0.773
Before features/support/hooks.rb:269 0.007
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.817
Then Tails is running from USB drive "old" 0.382
And all tps features are active 2.067
When I write some files expected to persist 1.744
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 3.521
And I take note of which tps features are available 0.586
And I shutdown Tails and wait for the computer to power off 4.378
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.430
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.012
Tags: @product
2:29.619
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.663
And I log in to a new session 20.061
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.388
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.309
Then the running Tails is installed on USB drive "to_upgrade" 19.290
And I unplug USB drive "to_upgrade" 0.249
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:326 7.900
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.420
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.793
Then all tps features from the old Tails version are active 1.647
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.363
And the expected persistent files created with the old Tails version are present in the filesystem 1.579
And all persistent directories from the old Tails version have safe access rights 2.522
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:1.541
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.728
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.360
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.055
And Tor is ready 43.120
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.647
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.990
Given I shutdown Tails and wait for the computer to power off 1:15.781
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.218
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.408
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.373
# 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.392
When the network is plugged 0.046
And Tor is ready 15.690
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.115
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.792
Given I shutdown Tails and wait for the computer to power off 4.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.388
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.964
And the file system changes introduced in version 6.3~testoverlayfs are present 0.641
And only the 6.3~testoverlayfs SquashFS delta is installed 0.125
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.034
And Tor is ready 18.686
Then the Upgrader considers the system as up-to-date 0.413
# 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.208
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.979
After features/support/hooks.rb:326 0.988
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
39.148
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.836
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 1.260
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 20.599
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.966
After features/support/hooks.rb:326 0.865
After features/support/hooks.rb:100 0.000