Project Number Date
test_Tails_ISO_devel 3333 23 Mar 2024, 12:12

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 18:6.753 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:38.016
Before features/support/hooks.rb:245 0.007
Given a computer 0.238
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 21.144
When I start Tails from USB drive "old" with network unplugged 1:11.557
Then the boot device has safe access rights 3.000
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.123
And udev-watchdog is monitoring the correct device 0.272
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:291 6.530
After features/support/hooks.rb:75 0.013
Tags: @product
2:8.203
Before features/support/hooks.rb:245 0.007
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:20.468
Then Tails is running from USB drive "old" 0.397
And I create a persistent partition 36.786
And I take note of which tps features are available 1.484
Then a Tails persistence partition exists on USB drive "old" 0.765
And I shutdown Tails and wait for the computer to power off 8.094
After features/support/hooks.rb:291 0.188
After features/support/hooks.rb:75 0.011
Tags: @product
2:40.125
Before features/support/hooks.rb:245 0.007
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.334
Then Tails is running from USB drive "old" 0.382
And all tps features are active 1.884
When I write some files expected to persist 1.754
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.861
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 4.019
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.496
After features/support/hooks.rb:291 0.166
After features/support/hooks.rb:75 0.011
Tags: @product
2:20.919
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.428
And I log in to a new session 16.123
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.354
And I plug USB drive "to_upgrade" 2.397
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.302
Then the running Tails is installed on USB drive "to_upgrade" 13.886
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:291 7.133
After features/support/hooks.rb:75 0.000
Tags: @product
2:18.828
Before features/support/hooks.rb:245 0.006
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.406
Then all tps features from the old Tails version are active 1.635
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 4.031
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.615
After features/support/hooks.rb:291 0.844
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
6:30.977
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.917
And no SquashFS delta is installed 0.068
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.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.039
And Tor is ready 16.715
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.582
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.434
Given I shutdown Tails and wait for the computer to power off 7.038
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.721
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.374
And the file system changes introduced in version 6.2~testoverlayfs are present 0.267
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.338
# 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.296
When the network is plugged 0.045
And Tor is ready 16.237
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.593
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.364
Given I shutdown Tails and wait for the computer to power off 4.111
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.319
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.899
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.039
And Tor is ready 18.957
Then the Upgrader considers the system as up-to-date 10.820
# 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.485
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.904
After features/support/hooks.rb:291 0.716
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
29.681
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.988
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.512
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 13.367
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.409
After features/support/hooks.rb:291 1.399
After features/support/hooks.rb:75 0.000