Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 45 17 Apr 2024, 06:49

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 17:17.074 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:34.602
Before features/support/hooks.rb:259 0.006
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 19.143
When I start Tails from USB drive "old" with network unplugged 1:10.537
Then the boot device has safe access rights 2.725
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.260
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:305 3.527
After features/support/hooks.rb:89 0.010
Tags: @product
2:1.013
Before features/support/hooks.rb:259 0.006
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:21.049
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 31.118
And I take note of which tps features are available 1.206
Then a Tails persistence partition exists on USB drive "old" 0.757
And I shutdown Tails and wait for the computer to power off 6.382
After features/support/hooks.rb:305 0.166
After features/support/hooks.rb:89 0.009
Tags: @product
2:25.661
Before features/support/hooks.rb:259 0.006
Given a computer 0.260
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.359
Then Tails is running from USB drive "old" 0.353
And all tps features are active 1.824
When I write some files expected to persist 1.598
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 2.239
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.385
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.592
After features/support/hooks.rb:305 0.107
After features/support/hooks.rb:89 0.009
Tags: @product
2:30.136
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.955
And I log in to a new session 14.311
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.275
And I plug USB drive "to_upgrade" 2.387
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.907
Then the running Tails is installed on USB drive "to_upgrade" 12.935
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.166
After features/support/hooks.rb:305 0.922
After features/support/hooks.rb:89 0.000
Tags: @product
1:58.560
Before features/support/hooks.rb:259 0.006
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.697
Then all tps features from the old Tails version are active 1.540
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 2.977
And the expected persistent files created with the old Tails version are present in the filesystem 1.283
And all persistent directories from the old Tails version have safe access rights 2.579
After features/support/hooks.rb:305 0.799
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:14.874
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.103
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.119
And Tor is ready 16.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.326
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.315
Given I shutdown Tails and wait for the computer to power off 8.773
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.863
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.968
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.257
# 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.252
When the network is plugged 0.041
And Tor is ready 18.736
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.156
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.658
Given I shutdown Tails and wait for the computer to power off 4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.028
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.948
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.037
And Tor is ready 45.457
Then the Upgrader considers the system as up-to-date 0.251
# 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 12.809
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.944
After features/support/hooks.rb:305 0.788
After features/support/hooks.rb:89 0.019
Tags: @product @automatic_upgrade
32.224
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.618
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.462
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 16.779
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.956
After features/support/hooks.rb:305 0.607
After features/support/hooks.rb:89 0.000