Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 94 04 Jun 2024, 06:42

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 20:10.405 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
2:20.399
Before features/support/hooks.rb:265 0.002
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.298
When I start Tails from USB drive "old" with network unplugged 1:44.276
Then the boot device has safe access rights 3.375
And Tails is running from USB drive "old" 0.379
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.380
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:311 7.332
After features/support/hooks.rb:100 0.007
Tags: @product
2:21.999
Before features/support/hooks.rb:265 0.004
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:33.825
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 35.876
And I take note of which tps features are available 2.591
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.339
After features/support/hooks.rb:311 0.218
After features/support/hooks.rb:100 0.005
Tags: @product
2:58.468
Before features/support/hooks.rb:265 0.002
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.555
Then Tails is running from USB drive "old" 0.360
And all tps features are active 2.483
When I write some files expected to persist 2.037
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.654
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.195
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.755
After features/support/hooks.rb:311 0.132
After features/support/hooks.rb:100 0.005
Tags: @product
2:26.899
Before features/support/hooks.rb:265 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.565
And I log in to a new session 19.437
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.482
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.477
Then the running Tails is installed on USB drive "to_upgrade" 16.864
And I unplug USB drive "to_upgrade" 0.404
And I unplug USB drive "__internal" 0.260
After features/support/hooks.rb:311 3.722
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.979
Before features/support/hooks.rb:265 0.003
Given a computer 0.724
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.375
Then all tps features from the old Tails version are active 1.664
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.608
And the expected persistent files created with the old Tails version are present in the filesystem 1.645
And all persistent directories from the old Tails version have safe access rights 2.615
After features/support/hooks.rb:311 0.814
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:48.188
Before features/support/hooks.rb:265 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.330
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.139
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.471
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.751
When the network is plugged 0.046
And Tor is ready 21.863
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.472
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.478
Given I shutdown Tails and wait for the computer to power off 9.112
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.959
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.502
And the file system changes introduced in version 6.2~testoverlayfs are present 0.392
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.374
# 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.295
When the network is plugged 0.035
And Tor is ready 16.638
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.228
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.980
Given I shutdown Tails and wait for the computer to power off 6.714
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.200
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.254
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.033
And Tor is ready 22.099
Then the Upgrader considers the system as up-to-date 0.368
# 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 15.751
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.948
After features/support/hooks.rb:311 0.752
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
52.470
Before features/support/hooks.rb:265 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 1.167
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 19.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.055
After features/support/hooks.rb:311 0.904
After features/support/hooks.rb:100 0.000