Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 14 20 Mar 2024, 17:29

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:5.295 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:31.613
Before features/support/hooks.rb:245 0.006
Given a computer 0.154
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 19.227
When I start Tails from USB drive "old" with network unplugged 1:7.405
Then the boot device has safe access rights 2.884
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.079
And udev-watchdog is monitoring the correct device 0.266
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:291 6.644
After features/support/hooks.rb:75 0.010
Tags: @product
1:58.753
Before features/support/hooks.rb:245 0.005
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:14.701
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 33.175
And I take note of which tps features are available 1.613
Then a Tails persistence partition exists on USB drive "old" 0.774
And I shutdown Tails and wait for the computer to power off 8.026
After features/support/hooks.rb:291 0.164
After features/support/hooks.rb:75 0.008
Tags: @product
2:30.063
Before features/support/hooks.rb:245 0.004
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:3.495
Then Tails is running from USB drive "old" 0.355
And all tps features are active 1.738
When I write some files expected to persist 1.552
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.665
And I take note of which tps features are available 0.369
And I shutdown Tails and wait for the computer to power off 4.077
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.040
After features/support/hooks.rb:291 0.135
After features/support/hooks.rb:75 0.009
Tags: @product
2:21.784
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.177
And I log in to a new session 17.454
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.166
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.807
Then the running Tails is installed on USB drive "to_upgrade" 13.274
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:291 3.551
After features/support/hooks.rb:75 0.000
Tags: @product
2:3.572
Before features/support/hooks.rb:245 0.006
Given a computer 0.146
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.514
Then all tps features from the old Tails version are active 1.583
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 2.965
And the expected persistent files created with the old Tails version are present in the filesystem 1.771
And all persistent directories from the old Tails version have safe access rights 2.273
After features/support/hooks.rb:291 0.919
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:4.929
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 12.736
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.056
And Tor is ready 15.990
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.928
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.048
Given I shutdown Tails and wait for the computer to power off 7.034
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.117
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.748
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# 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.279
When the network is plugged 0.067
And Tor is ready 15.636
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.171
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.110
Given I shutdown Tails and wait for the computer to power off 4.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.971
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 1.863
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.034
And Tor is ready 17.335
Then the Upgrader considers the system as up-to-date 0.238
# 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 13.573
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.924
After features/support/hooks.rb:291 0.740
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
34.578
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 10.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.612
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 16.802
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.646
After features/support/hooks.rb:291 0.749
After features/support/hooks.rb:75 0.000