Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 48 19 Apr 2024, 06:43

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:35.520 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:31.861
Before features/support/hooks.rb:259 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 18.437
When I start Tails from USB drive "old" with network unplugged 1:8.253
Then the boot device has safe access rights 2.917
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:305 3.565
After features/support/hooks.rb:89 0.011
Tags: @product
2:0.767
Before features/support/hooks.rb:259 0.007
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:16.002
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 33.527
And I take note of which tps features are available 1.286
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 8.725
After features/support/hooks.rb:305 0.137
After features/support/hooks.rb:89 0.009
Tags: @product
2:28.788
Before features/support/hooks.rb:259 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:1.330
Then Tails is running from USB drive "old" 0.375
And all tps features are active 2.153
When I write some files expected to persist 1.797
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.310
And all persistence configuration files have safe access rights 0.517
And all persistent directories from the old Tails version have safe access rights 2.535
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.203
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.885
After features/support/hooks.rb:305 0.151
After features/support/hooks.rb:89 0.009
Tags: @product
2:22.475
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 9.510
And I log in to a new session 18.195
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.318
And I plug USB drive "to_upgrade" 2.392
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.901
Then the running Tails is installed on USB drive "to_upgrade" 15.789
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.170
After features/support/hooks.rb:305 1.998
After features/support/hooks.rb:89 0.000
Tags: @product
2:10.667
Before features/support/hooks.rb:259 0.006
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.959
Then all tps features from the old Tails version are active 1.759
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 2.749
And the expected persistent files created with the old Tails version are present in the filesystem 1.440
And all persistent directories from the old Tails version have safe access rights 2.233
After features/support/hooks.rb:305 0.662
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
6:25.401
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.244
And no SquashFS delta is installed 0.213
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.059
And Tor is ready 19.439
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.184
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.552
Given I shutdown Tails and wait for the computer to power off 8.987
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.518
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.196
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
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.345
# 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.257
When the network is plugged 0.047
And Tor is ready 16.927
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.378
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.590
Given I shutdown Tails and wait for the computer to power off 4.152
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.925
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.029
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.035
And Tor is ready 19.607
Then the Upgrader considers the system as up-to-date 0.297
# 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 13.970
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.884
After features/support/hooks.rb:305 0.788
After features/support/hooks.rb:89 0.024
Tags: @product @automatic_upgrade
35.557
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.804
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.450
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 21.163
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.684
After features/support/hooks.rb:305 0.691
After features/support/hooks.rb:89 0.000