Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 58 28 Apr 2024, 06:38

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:29.257 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:1.400
Before features/support/hooks.rb:259 0.006
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 32.242
When I start Tails from USB drive "old" with network unplugged 1:23.342
Then the boot device has safe access rights 3.359
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.368
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:305 7.353
After features/support/hooks.rb:89 0.009
Tags: @product
2:12.248
Before features/support/hooks.rb:259 0.008
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:25.028
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 35.217
And I take note of which tps features are available 1.963
Then a Tails persistence partition exists on USB drive "old" 0.980
And I shutdown Tails and wait for the computer to power off 8.483
After features/support/hooks.rb:305 0.161
After features/support/hooks.rb:89 0.011
Tags: @product
3:14.283
Before features/support/hooks.rb:259 0.006
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.945
Then Tails is running from USB drive "old" 0.387
And all tps features are active 2.162
When I write some files expected to persist 1.712
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 2.941
And I take note of which tps features are available 0.490
And I shutdown Tails and wait for the computer to power off 4.620
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.131
After features/support/hooks.rb:305 0.147
After features/support/hooks.rb:89 0.014
Tags: @product
2:32.098
Before features/support/hooks.rb:259 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.568
And I log in to a new session 20.715
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.990
And I plug USB drive "to_upgrade" 2.558
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.041
Then the running Tails is installed on USB drive "to_upgrade" 19.840
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:305 3.569
After features/support/hooks.rb:89 0.000
Tags: @product
2:15.245
Before features/support/hooks.rb:259 0.016
Given a computer 0.238
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.691
Then all tps features from the old Tails version are active 1.648
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.058
And the expected persistent files created with the old Tails version are present in the filesystem 1.730
And all persistent directories from the old Tails version have safe access rights 2.550
After features/support/hooks.rb:305 0.773
After features/support/hooks.rb:89 0.012
Tags: @product @automatic_upgrade
6:37.301
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.041
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.092
And Tor is ready 21.936
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.777
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.105
Given I shutdown Tails and wait for the computer to power off 8.650
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.236
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.382
And the file system changes introduced in version 6.2~testoverlayfs are present 0.338
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.436
# 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.244
When the network is plugged 0.049
And Tor is ready 16.441
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.441
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.720
Given I shutdown Tails and wait for the computer to power off 4.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.143
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.250
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.041
And Tor is ready 17.415
Then the Upgrader considers the system as up-to-date 0.298
# 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 16.898
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.361
After features/support/hooks.rb:305 0.871
After features/support/hooks.rb:89 0.035
Tags: @product @automatic_upgrade
36.680
Before features/support/hooks.rb:259 0.021
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.165
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.536
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the signing key used by the Upgrader is outdated 1.191
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 15.229
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.393
After features/support/hooks.rb:305 0.906
After features/support/hooks.rb:89 0.000