Project Number Date
test_Tails_ISO_devel 3468 07 Aug 2024, 21:43

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 20:6.931 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:47.981
Before features/support/hooks.rb:269 0.009
Given a computer 1.374
And I create a 7200 MiB disk named "old" 0.111
And I plug USB drive "old" 1.150
And I write an old version of the Tails USB image to disk "old" 35.872
When I start Tails from USB drive "old" with network unplugged 2:5.034
Then the boot device has safe access rights 3.339
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.619
After features/support/hooks.rb:100 0.027
Tags: @product
2:9.097
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:28.084
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 31.165
And I take note of which tps features are available 1.911
Then a Tails persistence partition exists on USB drive "old" 0.894
And I shutdown Tails and wait for the computer to power off 6.494
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.552
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.753
Then Tails is running from USB drive "old" 0.377
And all tps features are active 2.115
When I write some files expected to persist 1.665
# 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.441
And all persistent directories from the old Tails version have safe access rights 3.769
And I take note of which tps features are available 0.546
And I shutdown Tails and wait for the computer to power off 4.366
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.081
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.778
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.963
And I log in to a new session 21.500
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.516
And I plug USB drive "to_upgrade" 2.491
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.210
Then the running Tails is installed on USB drive "to_upgrade" 19.635
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:326 3.307
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.077
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.998
Then all tps features from the old Tails version are active 1.617
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.553
And the expected persistent files created with the old Tails version are present in the filesystem 1.618
And all persistent directories from the old Tails version have safe access rights 2.710
After features/support/hooks.rb:326 0.583
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:42.768
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 12.632
And no SquashFS delta is installed 0.274
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.390
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.068
And Tor is ready 19.540
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.988
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.280
Given I shutdown Tails and wait for the computer to power off 9.071
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.372
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.231
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.343
# 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.283
When the network is plugged 0.064
And Tor is ready 18.451
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.601
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.398
Given I shutdown Tails and wait for the computer to power off 4.716
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.380
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.230
And the file system changes introduced in version 6.3~testoverlayfs are present 0.831
And only the 6.3~testoverlayfs SquashFS delta is installed 0.106
# 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.380
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.326
When the network is plugged 0.071
And Tor is ready 20.034
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 14.863
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.144
After features/support/hooks.rb:326 0.904
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
36.676
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.663
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.906
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 19.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.569
After features/support/hooks.rb:326 0.685
After features/support/hooks.rb:100 0.000