Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 49 20 Apr 2024, 06:31

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 18:38.663 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:41.711
Before features/support/hooks.rb:259 0.007
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 18.712
When I start Tails from USB drive "old" with network unplugged 1:17.907
Then the boot device has safe access rights 2.846
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:305 6.853
After features/support/hooks.rb:89 0.011
Tags: @product
1:55.142
Before features/support/hooks.rb:259 0.007
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login 1:13.508
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 32.323
And I take note of which tps features are available 1.338
Then a Tails persistence partition exists on USB drive "old" 0.733
And I shutdown Tails and wait for the computer to power off 6.673
After features/support/hooks.rb:305 0.159
After features/support/hooks.rb:89 0.011
Tags: @product
2:24.982
Before features/support/hooks.rb:259 0.007
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:58.296
Then Tails is running from USB drive "old" 0.311
And all tps features are active 1.868
When I write some files expected to persist 1.594
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 2.730
And I take note of which tps features are available 0.399
And I shutdown Tails and wait for the computer to power off 4.312
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.621
After features/support/hooks.rb:305 0.136
After features/support/hooks.rb:89 0.009
Tags: @product
2:21.345
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 10.440
And I log in to a new session 16.983
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.263
And I plug USB drive "to_upgrade" 2.378
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.786
Then the running Tails is installed on USB drive "to_upgrade" 13.116
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:305 3.544
After features/support/hooks.rb:89 0.000
Tags: @product
2:11.517
Before features/support/hooks.rb:259 0.009
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.469
Then all tps features from the old Tails version are active 1.622
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 2.994
And the expected persistent files created with the old Tails version are present in the filesystem 1.634
And all persistent directories from the old Tails version have safe access rights 2.285
After features/support/hooks.rb:305 0.972
After features/support/hooks.rb:89 0.013
Tags: @product @automatic_upgrade
7:28.978
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 10.883
And no SquashFS delta is installed 0.116
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.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.346
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.461
When the network is plugged 0.099
And Tor is ready 19.936
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.749
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.243
Given I shutdown Tails and wait for the computer to power off 1:5.949
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.129
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.123
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
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.460
# 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.258
When the network is plugged 0.049
And Tor is ready 18.973
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.820
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.130
Given I shutdown Tails and wait for the computer to power off 4.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.737
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.917
And the file system changes introduced in version 6.3~testoverlayfs are present 0.438
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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.047
And Tor is ready 19.065
Then the Upgrader considers the system as up-to-date 0.278
# 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.154
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.977
After features/support/hooks.rb:305 0.750
After features/support/hooks.rb:89 0.021
Tags: @product @automatic_upgrade
34.986
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 1.059
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 19.328
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.130
After features/support/hooks.rb:305 0.800
After features/support/hooks.rb:89 0.000