Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 15 21 Mar 2024, 06:14

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 16:14.476 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:27.426
Before features/support/hooks.rb:245 0.006
Given a computer 0.150
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 19.177
When I start Tails from USB drive "old" with network unplugged 1:3.450
Then the boot device has safe access rights 2.680
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.273
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:291 3.508
After features/support/hooks.rb:75 0.010
Tags: @product
1:52.660
Before features/support/hooks.rb:245 0.006
Given a computer 0.156
And I start Tails from USB drive "old" with network unplugged and I login 1:13.211
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 30.809
And I take note of which tps features are available 1.283
Then a Tails persistence partition exists on USB drive "old" 0.855
And I shutdown Tails and wait for the computer to power off 6.019
After features/support/hooks.rb:291 0.172
After features/support/hooks.rb:75 0.010
Tags: @product
2:22.155
Before features/support/hooks.rb:245 0.006
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:57.700
Then Tails is running from USB drive "old" 0.352
And all tps features are active 1.667
When I write some files expected to persist 1.506
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 2.278
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 3.038
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.465
After features/support/hooks.rb:291 0.100
After features/support/hooks.rb:75 0.009
Tags: @product
2:18.938
Before features/support/hooks.rb:245 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.519
And I log in to a new session 15.378
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.624
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.688
Then the running Tails is installed on USB drive "to_upgrade" 12.932
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:291 6.528
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.262
Before features/support/hooks.rb:245 0.006
Given a computer 0.156
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.241
Then all tps features from the old Tails version are active 1.216
And Tails is running from USB drive "to_upgrade" 0.273
And the boot device has safe access rights 3.765
And the expected persistent files created with the old Tails version are present in the filesystem 1.288
And all persistent directories from the old Tails version have safe access rights 2.320
After features/support/hooks.rb:291 1.015
After features/support/hooks.rb:75 0.010
5:47.421
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.847
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.039
And Tor is ready 15.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.298
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.740
Given I shutdown Tails and wait for the computer to power off 6.025
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.941
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.739
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.242
When the network is plugged 0.039
And Tor is ready 14.582
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.321
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.245
Given I shutdown Tails and wait for the computer to power off 4.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.007
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.564
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.044
And Tor is ready 17.249
Then the Upgrader considers the system as up-to-date 10.631
# 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 12.421
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.823
After features/support/hooks.rb:291 0.689
After features/support/hooks.rb:75 0.020
29.610
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.685
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.400
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 14.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.011
After features/support/hooks.rb:291 1.007
After features/support/hooks.rb:75 0.000