Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 90 30 May 2024, 13:47

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:38.329 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:18.375
Before features/support/hooks.rb:265 0.004
Given a computer 1.177
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 37.808
When I start Tails from USB drive "old" with network unplugged 1:34.089
Then the boot device has safe access rights 3.181
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:311 3.549
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.207
Before features/support/hooks.rb:265 0.005
Given a computer 0.380
And I start Tails from USB drive "old" with network unplugged and I login 1:27.316
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 37.106
And I take note of which tps features are available 1.579
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 8.590
After features/support/hooks.rb:311 0.176
After features/support/hooks.rb:100 0.010
Tags: @product
3:5.085
Before features/support/hooks.rb:265 0.005
Given a computer 0.265
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.612
Then Tails is running from USB drive "old" 0.367
And all tps features are active 2.168
When I write some files expected to persist 2.577
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.471
And all persistent directories from the old Tails version have safe access rights 2.658
And I take note of which tps features are available 0.821
And I shutdown Tails and wait for the computer to power off 4.221
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.658
After features/support/hooks.rb:311 0.173
After features/support/hooks.rb:100 0.012
Tags: @product
2:49.765
Before features/support/hooks.rb:265 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.467
And I log in to a new session 21.811
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.874
And I plug USB drive "to_upgrade" 2.480
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.683
Then the running Tails is installed on USB drive "to_upgrade" 22.949
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.255
After features/support/hooks.rb:311 2.680
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.374
Before features/support/hooks.rb:265 0.005
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.477
Then all tps features from the old Tails version are active 1.693
And Tails is running from USB drive "to_upgrade" 0.412
And the boot device has safe access rights 3.587
And the expected persistent files created with the old Tails version are present in the filesystem 1.476
And all persistent directories from the old Tails version have safe access rights 2.514
After features/support/hooks.rb:311 0.812
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:47.272
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.253
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.077
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.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.042
And Tor is ready 21.473
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.242
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.286
Given I shutdown Tails and wait for the computer to power off 11.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.191
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.357
# 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.260
When the network is plugged 0.036
And Tor is ready 19.766
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.201
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.206
Given I shutdown Tails and wait for the computer to power off 4.570
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.898
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.743
And the file system changes introduced in version 6.3~testoverlayfs are present 0.544
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.070
And Tor is ready 21.218
Then the Upgrader considers the system as up-to-date 0.342
# 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.750
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.060
After features/support/hooks.rb:311 0.697
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
53.247
Before features/support/hooks.rb:265 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.982
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.492
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 1.174
But a current signing key is available on our website 0.000
When the network is plugged 0.606
And Tor is ready 21.903
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.035
After features/support/hooks.rb:311 1.338
After features/support/hooks.rb:100 0.000