Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 80 22 May 2024, 06:51

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:33.684 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:41.067
Before features/support/hooks.rb:259 0.005
Given a computer 0.270
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 51.321
When I start Tails from USB drive "old" with network unplugged 1:44.383
Then the boot device has safe access rights 2.972
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:305 7.100
After features/support/hooks.rb:89 0.009
Tags: @product
2:18.878
Before features/support/hooks.rb:259 0.007
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:26.169
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 38.325
And I take note of which tps features are available 1.852
Then a Tails persistence partition exists on USB drive "old" 0.894
And I shutdown Tails and wait for the computer to power off 11.063
After features/support/hooks.rb:305 0.171
After features/support/hooks.rb:89 0.011
Tags: @product
2:55.295
Before features/support/hooks.rb:259 0.007
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.219
Then Tails is running from USB drive "old" 0.391
And all tps features are active 2.435
When I write some files expected to persist 1.988
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.610
And all persistent directories from the old Tails version have safe access rights 2.814
And I take note of which tps features are available 2.689
And I shutdown Tails and wait for the computer to power off 4.234
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.440
After features/support/hooks.rb:305 0.188
After features/support/hooks.rb:89 0.008
Tags: @product
2:53.867
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 30.719
And I log in to a new session 19.430
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.723
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.824
Then the running Tails is installed on USB drive "to_upgrade" 23.194
And I unplug USB drive "to_upgrade" 0.383
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:305 3.904
After features/support/hooks.rb:89 0.000
Tags: @product
2:24.323
Before features/support/hooks.rb:259 0.010
Given a computer 0.256
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.373
Then all tps features from the old Tails version are active 1.671
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.456
And the expected persistent files created with the old Tails version are present in the filesystem 1.658
And all persistent directories from the old Tails version have safe access rights 2.571
After features/support/hooks.rb:305 0.807
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
6:42.318
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.496
And no SquashFS delta is installed 0.293
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.426
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.039
And Tor is ready 23.744
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.642
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.035
Given I shutdown Tails and wait for the computer to power off 15.588
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.114
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.133
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.516
# 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.420
When the network is plugged 0.032
And Tor is ready 19.029
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.623
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.058
Given I shutdown Tails and wait for the computer to power off 4.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.122
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.143
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.083
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.043
And Tor is ready 19.605
Then the Upgrader considers the system as up-to-date 0.329
# 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.150
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.905
After features/support/hooks.rb:305 0.901
After features/support/hooks.rb:89 0.020
Tags: @product @automatic_upgrade
37.933
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 11.482
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.176
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.959
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 17.379
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.814
After features/support/hooks.rb:305 1.411
After features/support/hooks.rb:89 0.000