Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 86 26 May 2024, 16:17

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 19:46.986 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.547
Before features/support/hooks.rb:259 0.006
Given a computer 0.529
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.636
When I start Tails from USB drive "old" with network unplugged 1:40.131
Then the boot device has safe access rights 3.074
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.139
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:305 3.788
After features/support/hooks.rb:89 0.010
Tags: @product
2:15.745
Before features/support/hooks.rb:259 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:26.736
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 36.278
And I take note of which tps features are available 2.078
Then a Tails persistence partition exists on USB drive "old" 0.962
And I shutdown Tails and wait for the computer to power off 9.179
After features/support/hooks.rb:305 0.204
After features/support/hooks.rb:89 0.008
Tags: @product
3:1.599
Before features/support/hooks.rb:259 0.004
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.615
Then Tails is running from USB drive "old" 0.398
And all tps features are active 2.252
When I write some files expected to persist 2.020
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.450
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 5.054
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.463
After features/support/hooks.rb:305 0.149
After features/support/hooks.rb:89 0.010
Tags: @product
2:31.407
Before features/support/hooks.rb:259 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 14.874
And I log in to a new session 17.893
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.350
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.984
Then the running Tails is installed on USB drive "to_upgrade" 17.159
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.466
After features/support/hooks.rb:305 4.802
After features/support/hooks.rb:89 0.000
Tags: @product
2:11.263
Before features/support/hooks.rb:259 0.006
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.806
Then all tps features from the old Tails version are active 1.749
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.033
And the expected persistent files created with the old Tails version are present in the filesystem 1.489
And all persistent directories from the old Tails version have safe access rights 2.647
After features/support/hooks.rb:305 0.696
After features/support/hooks.rb:89 0.008
6:51.950
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.564
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.338
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.538
When the network is plugged 0.048
And Tor is ready 20.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.756
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.842
Given I shutdown Tails and wait for the computer to power off 8.827
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.102
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.228
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.282
When the network is plugged 0.043
And Tor is ready 21.008
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.324
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.862
Given I shutdown Tails and wait for the computer to power off 4.424
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.399
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.473
When the network is plugged 0.053
And Tor is ready 16.539
Then the Upgrader considers the system as up-to-date 10.795
# 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.460
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.854
After features/support/hooks.rb:305 0.780
After features/support/hooks.rb:89 0.022
36.472
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.044
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.525
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 18.818
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.659
After features/support/hooks.rb:305 0.742
After features/support/hooks.rb:89 0.000