Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 91 31 May 2024, 09:15

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:37.677 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:23.442
Before features/support/hooks.rb:265 0.006
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 36.088
When I start Tails from USB drive "old" with network unplugged 1:41.894
Then the boot device has safe access rights 3.152
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:311 3.847
After features/support/hooks.rb:100 0.011
Tags: @product
2:8.507
Before features/support/hooks.rb:265 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:23.806
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 34.814
And I take note of which tps features are available 1.775
Then a Tails persistence partition exists on USB drive "old" 0.845
And I shutdown Tails and wait for the computer to power off 6.697
After features/support/hooks.rb:311 0.172
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.163
Before features/support/hooks.rb:265 0.004
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.989
Then Tails is running from USB drive "old" 0.417
And all tps features are active 2.247
When I write some files expected to persist 1.930
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.979
And I take note of which tps features are available 0.560
And I shutdown Tails and wait for the computer to power off 6.504
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.670
After features/support/hooks.rb:311 0.133
After features/support/hooks.rb:100 0.011
Tags: @product
2:32.396
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.535
And I log in to a new session 20.274
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.568
And I plug USB drive "to_upgrade" 2.516
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.107
Then the running Tails is installed on USB drive "to_upgrade" 20.999
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:311 2.473
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.093
Before features/support/hooks.rb:265 0.006
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.940
Then all tps features from the old Tails version are active 1.659
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.309
And the expected persistent files created with the old Tails version are present in the filesystem 1.622
And all persistent directories from the old Tails version have safe access rights 4.031
After features/support/hooks.rb:311 0.759
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:44.508
Before features/support/hooks.rb:265 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.148
And no SquashFS delta is installed 0.136
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.380
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.034
And Tor is ready 19.255
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.915
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.411
Given I shutdown Tails and wait for the computer to power off 9.129
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.495
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.442
And the file system changes introduced in version 6.2~testoverlayfs are present 0.373
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.374
# 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.278
When the network is plugged 0.060
And Tor is ready 21.029
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.470
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.484
Given I shutdown Tails and wait for the computer to power off 4.437
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.083
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.190
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.066
And Tor is ready 18.601
Then the Upgrader considers the system as up-to-date 0.344
# 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.224
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.934
After features/support/hooks.rb:311 0.715
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
37.565
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 1.228
But a current signing key is available on our website 0.000
When the network is plugged 0.149
And Tor is ready 19.984
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.696
After features/support/hooks.rb:311 0.717
After features/support/hooks.rb:100 0.000