Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 12 20 Mar 2024, 06:58

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 17:17.451 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
1:49.331
Before features/support/hooks.rb:245 0.017
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 21.372
When I start Tails from USB drive "old" with network unplugged 1:22.887
Then the boot device has safe access rights 2.885
And Tails is running from USB drive "old" 0.288
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:291 3.548
After features/support/hooks.rb:75 0.033
Tags: @product
1:59.603
Before features/support/hooks.rb:245 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:14.979
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 34.790
And I take note of which tps features are available 1.512
Then a Tails persistence partition exists on USB drive "old" 0.732
And I shutdown Tails and wait for the computer to power off 7.113
After features/support/hooks.rb:291 0.167
After features/support/hooks.rb:75 0.010
Tags: @product
2:26.034
Before features/support/hooks.rb:245 0.006
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.355
Then Tails is running from USB drive "old" 0.439
And all tps features are active 1.831
When I write some files expected to persist 1.555
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.190
And I take note of which tps features are available 0.329
And I shutdown Tails and wait for the computer to power off 4.016
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.561
After features/support/hooks.rb:291 0.101
After features/support/hooks.rb:75 0.011
Tags: @product
2:19.641
Before features/support/hooks.rb:245 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 9.472
And I log in to a new session 16.420
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.648
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.896
Then the running Tails is installed on USB drive "to_upgrade" 13.412
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:291 6.510
After features/support/hooks.rb:75 0.000
Tags: @product
2:0.786
Before features/support/hooks.rb:245 0.008
Given a computer 0.154
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.278
Then all tps features from the old Tails version are active 1.542
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.301
And the expected persistent files created with the old Tails version are present in the filesystem 1.629
And all persistent directories from the old Tails version have safe access rights 2.537
After features/support/hooks.rb:291 0.874
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
6:8.211
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.591
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.583
When the network is plugged 0.034
And Tor is ready 18.802
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.302
Given I shutdown Tails and wait for the computer to power off 7.135
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.664
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.392
And the file system changes introduced in version 6.2~testoverlayfs are present 0.404
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.317
When the network is plugged 0.034
And Tor is ready 17.717
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.451
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.124
Given I shutdown Tails and wait for the computer to power off 4.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.811
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.863
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.040
And Tor is ready 18.874
Then the Upgrader considers the system as up-to-date 0.303
# 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.842
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.012
After features/support/hooks.rb:291 0.836
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
33.842
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 1.135
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 15.736
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.518
After features/support/hooks.rb:291 0.655
After features/support/hooks.rb:75 0.000