Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 101 11 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:8.821 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:54.329
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.755
When I start Tails from USB drive "old" with network unplugged 1:19.620
Then the boot device has safe access rights 2.744
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:315 3.530
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.877
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:28.688
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 33.945
And I take note of which tps features are available 1.813
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 8.127
After features/support/hooks.rb:315 0.186
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.734
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.884
Then Tails is running from USB drive "old" 0.329
And all tps features are active 1.817
When I write some files expected to persist 1.673
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.340
And all persistent directories from the old Tails version have safe access rights 2.570
And I take note of which tps features are available 0.371
And I shutdown Tails and wait for the computer to power off 4.362
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.979
After features/support/hooks.rb:315 0.128
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.460
Before features/support/hooks.rb:269 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.963
And I log in to a new session 19.441
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.754
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.544
Then the running Tails is installed on USB drive "to_upgrade" 18.955
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:315 2.014
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.715
Before features/support/hooks.rb:269 0.007
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.355
Then all tps features from the old Tails version are active 1.598
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.481
And the expected persistent files created with the old Tails version are present in the filesystem 1.411
And all persistent directories from the old Tails version have safe access rights 2.317
After features/support/hooks.rb:315 0.773
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:8.185
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 10.286
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.409
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.126
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.043
And Tor is ready 19.881
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.324
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.695
Given I shutdown Tails and wait for the computer to power off 8.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.004
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.887
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.113
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.396
# 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.237
When the network is plugged 0.029
And Tor is ready 18.907
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.035
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.982
Given I shutdown Tails and wait for the computer to power off 4.258
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.819
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.014
And the file system changes introduced in version 6.3~testoverlayfs are present 0.433
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.035
And Tor is ready 18.647
Then the Upgrader considers the system as up-to-date 0.289
# 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.043
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.876
After features/support/hooks.rb:315 0.741
After features/support/hooks.rb:100 0.068
Tags: @product @automatic_upgrade
33.517
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.444
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.367
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 1.006
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 17.586
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.009
After features/support/hooks.rb:315 0.926
After features/support/hooks.rb:100 0.000