Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 100 10 Jun 2024, 06:33

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:20.024 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:49.722
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.222
When I start Tails from USB drive "old" with network unplugged 1:14.642
Then the boot device has safe access rights 2.665
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:315 3.544
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.286
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:28.436
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 36.801
And I take note of which tps features are available 1.444
Then a Tails persistence partition exists on USB drive "old" 0.758
And I shutdown Tails and wait for the computer to power off 8.288
After features/support/hooks.rb:315 0.149
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.218
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.388
Then Tails is running from USB drive "old" 0.337
And all tps features are active 1.789
When I write some files expected to persist 1.540
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.205
And I take note of which tps features are available 0.413
And I shutdown Tails and wait for the computer to power off 4.671
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.006
After features/support/hooks.rb:315 0.155
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.038
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 9.881
And I log in to a new session 17.074
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.409
And I plug USB drive "to_upgrade" 2.458
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.704
Then the running Tails is installed on USB drive "to_upgrade" 15.142
And I unplug USB drive "to_upgrade" 0.180
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:315 2.429
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.323
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.630
Then all tps features from the old Tails version are active 1.441
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 2.937
And the expected persistent files created with the old Tails version are present in the filesystem 1.577
And all persistent directories from the old Tails version have safe access rights 2.255
After features/support/hooks.rb:315 0.838
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:29.222
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.986
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.047
And Tor is ready 20.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.394
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.839
Given I shutdown Tails and wait for the computer to power off 8.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.992
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.998
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
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.342
# 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.280
When the network is plugged 0.049
And Tor is ready 16.994
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.303
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.379
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.232
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.914
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.043
And Tor is ready 15.722
Then the Upgrader considers the system as up-to-date 11.179
# 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.262
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.901
After features/support/hooks.rb:315 0.726
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.214
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.473
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.957
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 19.400
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.925
After features/support/hooks.rb:315 0.617
After features/support/hooks.rb:100 0.000