Project Number Date
test_Tails_ISO_stable 5087 09 Sep 2024, 16:38

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 19:46.941 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:31.314
Before features/support/hooks.rb:269 0.006
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.588
When I start Tails from USB drive "old" with network unplugged 1:51.222
Then the boot device has safe access rights 3.898
And Tails is running from USB drive "old" 0.388
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.463
And I unplug USB drive "old" 0.275
After features/support/hooks.rb:326 3.623
After features/support/hooks.rb:100 0.013
Tags: @product
2:8.067
Before features/support/hooks.rb:269 0.009
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login 1:25.312
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 31.270
And I take note of which tps features are available 1.464
Then a Tails persistence partition exists on USB drive "old" 0.859
And I shutdown Tails and wait for the computer to power off 8.542
After features/support/hooks.rb:326 0.278
After features/support/hooks.rb:100 0.035
Tags: @product
2:56.618
Before features/support/hooks.rb:269 0.007
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.363
Then Tails is running from USB drive "old" 0.367
And all tps features are active 2.123
When I write some files expected to persist 1.620
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.433
And all persistence configuration files have safe access rights 0.525
And all persistent directories from the old Tails version have safe access rights 2.619
And I take note of which tps features are available 0.494
And I shutdown Tails and wait for the computer to power off 4.200
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.650
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.930
Before features/support/hooks.rb:269 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 14.372
And I log in to a new session 21.945
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.152
And I plug USB drive "to_upgrade" 2.535
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.725
Then the running Tails is installed on USB drive "to_upgrade" 23.726
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.257
After features/support/hooks.rb:326 5.274
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.853
Before features/support/hooks.rb:269 0.006
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.695
Then all tps features from the old Tails version are active 1.840
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 3.230
And the expected persistent files created with the old Tails version are present in the filesystem 1.784
And all persistent directories from the old Tails version have safe access rights 2.695
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:37.547
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.776
And no SquashFS delta is installed 0.221
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.552
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.366
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.073
And Tor is ready 19.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.767
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.181
Given I shutdown Tails and wait for the computer to power off 11.209
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.683
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.941
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.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.250
When the network is plugged 0.074
And Tor is ready 21.662
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.192
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.220
Given I shutdown Tails and wait for the computer to power off 4.669
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.314
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.113
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.071
And Tor is ready 18.947
Then the Upgrader considers the system as up-to-date 10.861
# 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.442
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.974
After features/support/hooks.rb:326 0.826
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
32.609
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 10.398
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.508
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.826
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 15.696
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.057
After features/support/hooks.rb:326 0.658
After features/support/hooks.rb:100 0.000