Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 89 29 May 2024, 08:01

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:31.702 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:12.591
Before features/support/hooks.rb:259 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.437
When I start Tails from USB drive "old" with network unplugged 1:38.098
Then the boot device has safe access rights 2.838
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:305 3.552
After features/support/hooks.rb:89 0.009
Tags: @product
2:6.344
Before features/support/hooks.rb:259 0.006
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login 1:19.463
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 35.766
And I take note of which tps features are available 1.472
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.328
After features/support/hooks.rb:305 0.166
After features/support/hooks.rb:89 0.011
Tags: @product
2:52.094
Before features/support/hooks.rb:259 0.004
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.164
Then Tails is running from USB drive "old" 0.381
And all tps features are active 2.218
When I write some files expected to persist 1.712
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.721
And I take note of which tps features are available 0.457
And I shutdown Tails and wait for the computer to power off 4.318
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.323
After features/support/hooks.rb:305 0.109
After features/support/hooks.rb:89 0.009
Tags: @product
2:37.959
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 11.905
And I log in to a new session 19.105
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.351
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.780
Then the running Tails is installed on USB drive "to_upgrade" 22.552
And I unplug USB drive "to_upgrade" 0.401
And I unplug USB drive "__internal" 0.431
After features/support/hooks.rb:305 1.869
After features/support/hooks.rb:89 0.000
Tags: @product
2:10.662
Before features/support/hooks.rb:259 0.006
Given a computer 0.877
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.571
Then all tps features from the old Tails version are active 1.710
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.061
And the expected persistent files created with the old Tails version are present in the filesystem 1.331
And all persistent directories from the old Tails version have safe access rights 2.772
After features/support/hooks.rb:305 0.681
After features/support/hooks.rb:89 0.010
6:53.525
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 19.985
And no SquashFS delta is installed 0.209
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.167
And Tor is ready 20.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.757
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.744
Given I shutdown Tails and wait for the computer to power off 10.735
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.618
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.123
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.223
When the network is plugged 0.043
And Tor is ready 21.281
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.973
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.148
Given I shutdown Tails and wait for the computer to power off 4.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.725
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.999
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.422
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.040
And Tor is ready 17.644
Then the Upgrader considers the system as up-to-date 0.314
# 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.584
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.933
After features/support/hooks.rb:305 0.706
After features/support/hooks.rb:89 0.022
38.524
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.002
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.077
And the signing key used by the Upgrader is outdated 0.497
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 20.987
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.610
After features/support/hooks.rb:305 0.922
After features/support/hooks.rb:89 0.000