Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 32 06 Apr 2024, 06:19

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:41.298 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.189
Before features/support/hooks.rb:259 0.008
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 20.174
When I start Tails from USB drive "old" with network unplugged 1:23.525
Then the boot device has safe access rights 3.191
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.350
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:305 6.786
After features/support/hooks.rb:89 0.045
Tags: @product
2:8.750
Before features/support/hooks.rb:259 0.013
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:18.642
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 38.464
And I take note of which tps features are available 1.359
Then a Tails persistence partition exists on USB drive "old" 0.752
And I shutdown Tails and wait for the computer to power off 8.968
After features/support/hooks.rb:305 0.168
After features/support/hooks.rb:89 0.010
Tags: @product
2:32.802
Before features/support/hooks.rb:259 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.630
Then Tails is running from USB drive "old" 0.338
And all tps features are active 2.018
When I write some files expected to persist 1.570
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.692
And I take note of which tps features are available 0.406
And I shutdown Tails and wait for the computer to power off 4.386
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.013
After features/support/hooks.rb:305 0.138
After features/support/hooks.rb:89 0.008
Tags: @product
2:18.745
Before features/support/hooks.rb:259 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.829
And I log in to a new session 16.333
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.259
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.738
Then the running Tails is installed on USB drive "to_upgrade" 13.778
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:305 3.579
After features/support/hooks.rb:89 0.000
Tags: @product
2:5.136
Before features/support/hooks.rb:259 0.009
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.977
Then all tps features from the old Tails version are active 1.477
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.024
And the expected persistent files created with the old Tails version are present in the filesystem 1.352
And all persistent directories from the old Tails version have safe access rights 2.762
After features/support/hooks.rb:305 0.861
After features/support/hooks.rb:89 0.011
6:12.743
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 10.655
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.055
And Tor is ready 17.188
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.445
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.731
Given I shutdown Tails and wait for the computer to power off 9.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.706
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.221
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.276
When the network is plugged 0.036
And Tor is ready 18.699
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.005
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.621
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.841
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.160
And the file system changes introduced in version 6.3~testoverlayfs are present 0.741
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.355
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.043
And Tor is ready 14.820
Then the Upgrader considers the system as up-to-date 0.235
# 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.205
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.903
After features/support/hooks.rb:305 0.873
After features/support/hooks.rb:89 0.019
33.931
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.842
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.383
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.517
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 16.069
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.021
After features/support/hooks.rb:305 0.665
After features/support/hooks.rb:89 0.000