Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 22 27 Mar 2024, 06:26

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 17:30.541 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:34.972
Before features/support/hooks.rb:245 0.009
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 21.941
When I start Tails from USB drive "old" with network unplugged 1:7.856
Then the boot device has safe access rights 2.831
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:291 3.715
After features/support/hooks.rb:75 0.020
Tags: @product
2:1.007
Before features/support/hooks.rb:245 0.011
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:13.079
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 34.646
And I take note of which tps features are available 1.391
Then a Tails persistence partition exists on USB drive "old" 0.760
And I shutdown Tails and wait for the computer to power off 10.555
After features/support/hooks.rb:291 0.192
After features/support/hooks.rb:75 0.009
Tags: @product
2:28.212
Before features/support/hooks.rb:245 0.006
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.817
Then Tails is running from USB drive "old" 0.354
And all tps features are active 1.821
When I write some files expected to persist 1.744
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.714
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 4.413
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.127
After features/support/hooks.rb:291 0.121
After features/support/hooks.rb:75 0.009
Tags: @product
2:18.597
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 10.632
And I log in to a new session 14.136
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.473
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.538
Then the running Tails is installed on USB drive "to_upgrade" 12.970
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:291 6.493
After features/support/hooks.rb:75 0.000
Tags: @product
2:1.708
Before features/support/hooks.rb:245 0.007
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.872
Then all tps features from the old Tails version are active 1.659
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.381
And the expected persistent files created with the old Tails version are present in the filesystem 1.742
And all persistent directories from the old Tails version have safe access rights 2.472
After features/support/hooks.rb:291 0.674
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:34.276
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 38.079
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.059
And Tor is ready 17.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.033
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.740
Given I shutdown Tails and wait for the computer to power off 6.773
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.152
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.049
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.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.273
# 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.291
When the network is plugged 0.065
And Tor is ready 15.272
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.693
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.101
Given I shutdown Tails and wait for the computer to power off 4.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.993
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.925
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.057
And Tor is ready 17.135
Then the Upgrader considers the system as up-to-date 10.616
# 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.724
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.853
After features/support/hooks.rb:291 0.724
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
31.767
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.652
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.796
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 15.991
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.892
After features/support/hooks.rb:291 0.621
After features/support/hooks.rb:75 0.000