Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 88 28 May 2024, 06:59

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:10.487 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:9.133
Before features/support/hooks.rb:259 0.007
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 30.722
When I start Tails from USB drive "old" with network unplugged 1:32.366
Then the boot device has safe access rights 3.614
And Tails is running from USB drive "old" 0.413
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:305 7.109
After features/support/hooks.rb:89 0.012
Tags: @product
2:22.165
Before features/support/hooks.rb:259 0.008
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:32.608
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 38.218
And I take note of which tps features are available 1.570
Then a Tails persistence partition exists on USB drive "old" 0.822
And I shutdown Tails and wait for the computer to power off 8.340
After features/support/hooks.rb:305 0.199
After features/support/hooks.rb:89 0.037
Tags: @product
3:3.622
Before features/support/hooks.rb:259 0.013
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.068
Then Tails is running from USB drive "old" 0.444
And all tps features are active 2.772
When I write some files expected to persist 2.170
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 2.709
And I take note of which tps features are available 0.971
And I shutdown Tails and wait for the computer to power off 4.223
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.347
After features/support/hooks.rb:305 0.115
After features/support/hooks.rb:89 0.009
Tags: @product
2:31.645
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 10.689
And I log in to a new session 19.781
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.594
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.914
Then the running Tails is installed on USB drive "to_upgrade" 18.769
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.185
After features/support/hooks.rb:305 2.436
After features/support/hooks.rb:89 0.000
Tags: @product
2:16.120
Before features/support/hooks.rb:259 0.005
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.120
Then all tps features from the old Tails version are active 1.716
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.637
And the expected persistent files created with the old Tails version are present in the filesystem 1.543
And all persistent directories from the old Tails version have safe access rights 2.553
After features/support/hooks.rb:305 0.737
After features/support/hooks.rb:89 0.010
7:11.667
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 31.325
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.459
And Tor is ready 17.958
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.304
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.415
Given I shutdown Tails and wait for the computer to power off 11.420
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.541
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 6.956
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.304
When the network is plugged 0.471
And Tor is ready 19.361
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.982
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.834
Given I shutdown Tails and wait for the computer to power off 6.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.466
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.145
And the file system changes introduced in version 6.3~testoverlayfs are present 0.615
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.615
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.042
And Tor is ready 19.008
Then the Upgrader considers the system as up-to-date 0.347
# 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.416
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.787
After features/support/hooks.rb:89 0.024
36.132
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 10.420
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.602
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 18.950
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.731
After features/support/hooks.rb:305 0.784
After features/support/hooks.rb:89 0.000