Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 9 19 Mar 2024, 23:03

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 16:53.843 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:38.625
Before features/support/hooks.rb:245 0.006
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 19.125
When I start Tails from USB drive "old" with network unplugged 1:14.586
Then the boot device has safe access rights 2.740
And Tails is running from USB drive "old" 0.281
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:291 9.742
After features/support/hooks.rb:75 0.010
Tags: @product
1:51.657
Before features/support/hooks.rb:245 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:12.899
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 30.116
And I take note of which tps features are available 1.385
Then a Tails persistence partition exists on USB drive "old" 0.720
And I shutdown Tails and wait for the computer to power off 6.062
After features/support/hooks.rb:291 0.165
After features/support/hooks.rb:75 0.009
Tags: @product
2:31.082
Before features/support/hooks.rb:245 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.474
Then Tails is running from USB drive "old" 0.336
And all tps features are active 1.895
When I write some files expected to persist 1.671
# 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.336
And all persistent directories from the old Tails version have safe access rights 2.701
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.018
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.732
After features/support/hooks.rb:291 0.104
After features/support/hooks.rb:75 0.009
Tags: @product
2:20.500
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.825
And I log in to a new session 18.119
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.466
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.387
Then the running Tails is installed on USB drive "to_upgrade" 12.910
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:291 3.523
After features/support/hooks.rb:75 0.000
Tags: @product
1:55.456
Before features/support/hooks.rb:245 0.005
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.055
Then all tps features from the old Tails version are active 1.427
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 2.710
And the expected persistent files created with the old Tails version are present in the filesystem 1.590
And all persistent directories from the old Tails version have safe access rights 2.205
After features/support/hooks.rb:291 0.851
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:4.578
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.867
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.529
When the network is plugged 0.062
And Tor is ready 19.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.235
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.549
Given I shutdown Tails and wait for the computer to power off 6.022
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.983
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.764
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.286
When the network is plugged 0.038
And Tor is ready 15.579
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.578
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.102
Given I shutdown Tails and wait for the computer to power off 4.018
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.410
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.831
And the file system changes introduced in version 6.3~testoverlayfs are present 0.460
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.279
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.039
And Tor is ready 17.146
Then the Upgrader considers the system as up-to-date 0.231
# 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.379
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.818
After features/support/hooks.rb:291 0.676
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
31.942
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.558
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.817
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 15.968
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.180
After features/support/hooks.rb:291 0.652
After features/support/hooks.rb:75 0.000