Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 62 02 May 2024, 06: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:25.866 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:21.695
Before features/support/hooks.rb:259 0.005
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.971
When I start Tails from USB drive "old" with network unplugged 1:45.387
Then the boot device has safe access rights 3.023
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:305 3.508
After features/support/hooks.rb:89 0.008
Tags: @product
2:10.395
Before features/support/hooks.rb:259 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:20.055
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 38.326
And I take note of which tps features are available 2.218
Then a Tails persistence partition exists on USB drive "old" 0.804
And I shutdown Tails and wait for the computer to power off 8.426
After features/support/hooks.rb:305 0.214
After features/support/hooks.rb:89 0.008
Tags: @product
2:52.459
Before features/support/hooks.rb:259 0.004
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.094
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.055
When I write some files expected to persist 1.691
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.461
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 4.344
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.218
After features/support/hooks.rb:305 0.153
After features/support/hooks.rb:89 0.008
Tags: @product
2:35.805
Before features/support/hooks.rb:259 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.904
And I log in to a new session 21.051
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.634
And I plug USB drive "to_upgrade" 2.625
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.950
Then the running Tails is installed on USB drive "to_upgrade" 20.224
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:305 2.092
After features/support/hooks.rb:89 0.000
Tags: @product
2:21.850
Before features/support/hooks.rb:259 0.005
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.982
Then all tps features from the old Tails version are active 1.609
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 2.946
And the expected persistent files created with the old Tails version are present in the filesystem 1.376
And all persistent directories from the old Tails version have safe access rights 2.440
After features/support/hooks.rb:305 0.730
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
7:26.291
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 11.258
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
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.458
When the network is plugged 0.067
And Tor is ready 18.137
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.782
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.031
Given I shutdown Tails and wait for the computer to power off 1:17.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.298
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.175
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.036
And Tor is ready 18.193
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.755
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.777
Given I shutdown Tails and wait for the computer to power off 4.392
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.092
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.157
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.051
And Tor is ready 16.170
Then the Upgrader considers the system as up-to-date 10.760
# 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.471
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.906
After features/support/hooks.rb:305 0.784
After features/support/hooks.rb:89 0.016
Tags: @product @automatic_upgrade
37.367
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 13.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.465
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 16.795
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.665
After features/support/hooks.rb:305 0.734
After features/support/hooks.rb:89 0.000