Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 98 08 Jun 2024, 06:21

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:53.820 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:52.886
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.057
When I start Tails from USB drive "old" with network unplugged 1:17.855
Then the boot device has safe access rights 2.759
And Tails is running from USB drive "old" 0.285
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:315 3.472
After features/support/hooks.rb:100 0.067
Tags: @product
2:4.535
Before features/support/hooks.rb:269 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:19.130
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 34.685
And I take note of which tps features are available 1.344
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 8.120
After features/support/hooks.rb:315 0.185
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.067
Before features/support/hooks.rb:269 0.007
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.362
Then Tails is running from USB drive "old" 0.382
And all tps features are active 1.908
When I write some files expected to persist 1.606
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
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.358
And I take note of which tps features are available 0.404
And I shutdown Tails and wait for the computer to power off 4.282
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.998
After features/support/hooks.rb:315 0.121
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.767
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.135
And I log in to a new session 16.982
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.180
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.043
Then the running Tails is installed on USB drive "to_upgrade" 18.593
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.185
After features/support/hooks.rb:315 2.229
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.262
Before features/support/hooks.rb:269 0.007
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.551
Then all tps features from the old Tails version are active 1.421
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.164
And the expected persistent files created with the old Tails version are present in the filesystem 1.350
And all persistent directories from the old Tails version have safe access rights 2.254
After features/support/hooks.rb:315 0.706
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:16.598
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.571
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.055
And Tor is ready 16.874
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.488
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.681
Given I shutdown Tails and wait for the computer to power off 8.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.936
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.112
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.248
When the network is plugged 0.034
And Tor is ready 16.972
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.989
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.584
Given I shutdown Tails and wait for the computer to power off 4.604
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.619
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.740
And the file system changes introduced in version 6.3~testoverlayfs are present 0.508
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.355
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.043
And Tor is ready 15.339
Then the Upgrader considers the system as up-to-date 10.750
# 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.516
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.833
After features/support/hooks.rb:315 0.764
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
33.701
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.843
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 1.328
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 15.828
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.290
After features/support/hooks.rb:315 1.432
After features/support/hooks.rb:100 0.000