Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 92 02 Jun 2024, 06:40

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:30.831 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:56.320
Before features/support/hooks.rb:265 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.542
When I start Tails from USB drive "old" with network unplugged 1:21.762
Then the boot device has safe access rights 2.821
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.276
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:311 7.079
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.635
Before features/support/hooks.rb:265 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:20.074
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 35.515
And I take note of which tps features are available 1.368
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 8.385
After features/support/hooks.rb:311 0.155
After features/support/hooks.rb:100 0.013
Tags: @product
2:42.653
Before features/support/hooks.rb:265 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.027
Then Tails is running from USB drive "old" 0.365
And all tps features are active 1.842
When I write some files expected to persist 1.748
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.577
And I take note of which tps features are available 0.391
And I shutdown Tails and wait for the computer to power off 4.344
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.565
After features/support/hooks.rb:311 0.151
After features/support/hooks.rb:100 0.011
Tags: @product
2:26.020
Before features/support/hooks.rb:265 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.064
And I log in to a new session 17.824
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.646
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.719
Then the running Tails is installed on USB drive "to_upgrade" 19.957
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:311 2.066
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.228
Before features/support/hooks.rb:265 0.007
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.993
Then all tps features from the old Tails version are active 1.693
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.023
And the expected persistent files created with the old Tails version are present in the filesystem 1.708
And all persistent directories from the old Tails version have safe access rights 2.270
After features/support/hooks.rb:311 0.671
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:25.821
Before features/support/hooks.rb:265 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.841
And no SquashFS delta is installed 0.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.046
And Tor is ready 20.716
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.485
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.266
Given I shutdown Tails and wait for the computer to power off 8.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.427
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.231
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# 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.273
When the network is plugged 0.045
And Tor is ready 20.988
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.386
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.787
Given I shutdown Tails and wait for the computer to power off 4.275
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.965
Then Tails is running version 6.3~testoverlayfs 0.036
And all tps features are active 1.971
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.043
And Tor is ready 21.759
Then the Upgrader considers the system as up-to-date 0.330
# 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.502
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.947
After features/support/hooks.rb:311 0.810
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
34.151
Before features/support/hooks.rb:265 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.479
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 1.636
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 19.386
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.430
After features/support/hooks.rb:311 1.268
After features/support/hooks.rb:100 0.000