Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 111 19 Jun 2024, 06:52

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:15.852 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:38.395
Before features/support/hooks.rb:269 0.007
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.359
When I start Tails from USB drive "old" with network unplugged 2:3.086
Then the boot device has safe access rights 3.478
And Tails is running from USB drive "old" 0.416
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 3.752
After features/support/hooks.rb:100 0.010
Tags: @product
2:19.077
Before features/support/hooks.rb:269 0.009
Given a computer 0.317
And I start Tails from USB drive "old" with network unplugged and I login 1:33.851
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 33.385
And I take note of which tps features are available 1.854
Then a Tails persistence partition exists on USB drive "old" 0.890
And I shutdown Tails and wait for the computer to power off 8.406
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.262
Before features/support/hooks.rb:269 0.006
Given a computer 0.266
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.313
Then Tails is running from USB drive "old" 0.327
And all tps features are active 2.240
When I write some files expected to persist 1.619
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.700
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 4.510
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.230
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.011
Tags: @product
2:29.878
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.362
And I log in to a new session 17.634
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.539
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.475
Then the running Tails is installed on USB drive "to_upgrade" 17.906
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.266
After features/support/hooks.rb:326 6.739
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.520
Before features/support/hooks.rb:269 0.008
Given a computer 0.249
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.233
Then all tps features from the old Tails version are active 1.723
And Tails is running from USB drive "to_upgrade" 0.438
And the boot device has safe access rights 3.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.584
And all persistent directories from the old Tails version have safe access rights 2.849
After features/support/hooks.rb:326 1.261
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:58.563
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 14.822
And no SquashFS delta is installed 0.659
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.053
And Tor is ready 19.408
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.918
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.663
Given I shutdown Tails and wait for the computer to power off 8.941
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.058
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.427
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.314
When the network is plugged 0.055
And Tor is ready 19.828
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.994
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.868
Given I shutdown Tails and wait for the computer to power off 4.477
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.923
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.371
And the file system changes introduced in version 6.3~testoverlayfs are present 0.549
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.345
When the network is plugged 0.061
And Tor is ready 46.353
Then the Upgrader considers the system as up-to-date 0.310
# 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 13.754
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.049
After features/support/hooks.rb:326 0.808
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
36.154
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 14.522
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.786
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 14.874
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.532
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.000