Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 63 03 May 2024, 06:47

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:34.481 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:13.065
Before features/support/hooks.rb:259 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.605
When I start Tails from USB drive "old" with network unplugged 1:36.953
Then the boot device has safe access rights 3.155
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.361
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:305 7.180
After features/support/hooks.rb:89 0.010
Tags: @product
2:18.051
Before features/support/hooks.rb:259 0.006
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:28.749
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 37.076
And I take note of which tps features are available 1.496
Then a Tails persistence partition exists on USB drive "old" 0.974
And I shutdown Tails and wait for the computer to power off 9.182
After features/support/hooks.rb:305 0.158
After features/support/hooks.rb:89 0.013
Tags: @product
2:58.885
Before features/support/hooks.rb:259 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.267
Then Tails is running from USB drive "old" 0.334
And all tps features are active 1.922
When I write some files expected to persist 1.761
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 3.055
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 4.334
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.969
After features/support/hooks.rb:305 0.140
After features/support/hooks.rb:89 0.010
Tags: @product
2:24.759
Before features/support/hooks.rb:259 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 9.902
And I log in to a new session 17.892
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.542
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.445
Then the running Tails is installed on USB drive "to_upgrade" 16.210
And I unplug USB drive "to_upgrade" 0.174
And I unplug USB drive "__internal" 0.169
After features/support/hooks.rb:305 2.927
After features/support/hooks.rb:89 0.000
Tags: @product
2:13.252
Before features/support/hooks.rb:259 0.006
Given a computer 0.259
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.681
Then all tps features from the old Tails version are active 1.765
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.197
And the expected persistent files created with the old Tails version are present in the filesystem 1.628
And all persistent directories from the old Tails version have safe access rights 2.413
After features/support/hooks.rb:305 0.809
After features/support/hooks.rb:89 0.010
6:52.741
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.999
And no SquashFS delta is installed 0.138
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.946
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.073
And Tor is ready 21.070
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.656
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.620
Given I shutdown Tails and wait for the computer to power off 8.760
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.774
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.013
And the file system changes introduced in version 6.2~testoverlayfs are present 0.267
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.277
When the network is plugged 0.057
And Tor is ready 18.160
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.437
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.490
Given I shutdown Tails and wait for the computer to power off 4.660
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.404
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.059
And the file system changes introduced in version 6.3~testoverlayfs are present 0.641
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.039
And Tor is ready 46.063
Then the Upgrader considers the system as up-to-date 0.292
# 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.862
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.055
After features/support/hooks.rb:305 0.706
After features/support/hooks.rb:89 0.017
33.725
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.628
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.448
But a current signing key is available on our website 0.000
When the network is plugged 0.111
And Tor is ready 18.028
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.121
After features/support/hooks.rb:305 1.334
After features/support/hooks.rb:89 0.000