Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 102 12 Jun 2024, 06:37

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:13.361 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:1.841
Before features/support/hooks.rb:269 0.007
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.495
When I start Tails from USB drive "old" with network unplugged 1:25.206
Then the boot device has safe access rights 2.916
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:320 7.055
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.497
Before features/support/hooks.rb:269 0.006
Given a computer 0.314
And I start Tails from USB drive "old" with network unplugged and I login 1:23.312
Then Tails is running from USB drive "old" 0.363
And I create a persistent partition 33.749
And I take note of which tps features are available 1.577
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.358
After features/support/hooks.rb:320 0.158
After features/support/hooks.rb:100 0.008
Tags: @product
2:49.597
Before features/support/hooks.rb:269 0.006
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.084
Then Tails is running from USB drive "old" 0.414
And all tps features are active 1.843
When I write some files expected to persist 1.669
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.552
And all persistent directories from the old Tails version have safe access rights 2.596
And I take note of which tps features are available 0.388
And I shutdown Tails and wait for the computer to power off 4.313
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.222
After features/support/hooks.rb:320 0.128
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.703
Before features/support/hooks.rb:269 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 10.915
And I log in to a new session 17.340
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.478
And I plug USB drive "to_upgrade" 2.399
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.071
Then the running Tails is installed on USB drive "to_upgrade" 17.090
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:320 3.524
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.462
Before features/support/hooks.rb:269 0.007
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.412
Then all tps features from the old Tails version are active 1.575
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 3.051
And the expected persistent files created with the old Tails version are present in the filesystem 1.372
And all persistent directories from the old Tails version have safe access rights 2.560
After features/support/hooks.rb:320 0.898
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:8.255
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.022
And no SquashFS delta is installed 0.179
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
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.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.040
And Tor is ready 20.155
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.396
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.989
Given I shutdown Tails and wait for the computer to power off 8.701
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.846
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.054
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
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.478
# 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.262
When the network is plugged 0.034
And Tor is ready 21.351
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.678
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.054
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:2.232
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.958
And the file system changes introduced in version 6.3~testoverlayfs are present 0.592
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.180
And Tor is ready 18.341
Then the Upgrader considers the system as up-to-date 0.329
# 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.995
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.905
After features/support/hooks.rb:320 0.839
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
34.001
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.772
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.964
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 17.453
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.388
After features/support/hooks.rb:320 1.066
After features/support/hooks.rb:100 0.000