Project Number Date
test_Tails_ISO_stable 5318 06 Dec 2024, 12:25

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 19:2.460 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:6.967
Before features/support/hooks.rb:269 0.006
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.433
When I start Tails from USB drive "old" with network unplugged 1:30.954
Then the boot device has safe access rights 3.173
And Tails is running from USB drive "old" 0.450
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 7.213
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.560
Before features/support/hooks.rb:269 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:22.172
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 31.508
And I take note of which tps features are available 1.347
Then a Tails persistence partition exists on USB drive "old" 0.793
And I shutdown Tails and wait for the computer to power off 8.280
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.904
Before features/support/hooks.rb:269 0.006
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.876
Then Tails is running from USB drive "old" 1.073
And all tps features are active 1.960
When I write some files expected to persist 1.527
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.343
And I take note of which tps features are available 0.385
And I shutdown Tails and wait for the computer to power off 4.737
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.222
After features/support/hooks.rb:326 0.096
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.038
Before features/support/hooks.rb:269 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.865
And I log in to a new session 19.214
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.016
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.240
Then the running Tails is installed on USB drive "to_upgrade" 22.901
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.309
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.053
Before features/support/hooks.rb:269 0.006
Given a computer 0.238
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.431
Then all tps features from the old Tails version are active 1.707
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.378
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.564
After features/support/hooks.rb:326 0.696
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:36.055
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.777
And no SquashFS delta is installed 0.293
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.064
And Tor is ready 25.067
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.378
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.465
Given I shutdown Tails and wait for the computer to power off 8.469
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.779
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 1.962
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.279
When the network is plugged 0.078
And Tor is ready 18.356
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.520
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.659
Given I shutdown Tails and wait for the computer to power off 4.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.193
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.822
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.549
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.349
When the network is plugged 0.070
And Tor is ready 17.973
Then the Upgrader considers the system as up-to-date 10.957
# 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 14.252
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.961
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.879
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.989
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.450
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.837
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 20.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.506
After features/support/hooks.rb:326 0.659
After features/support/hooks.rb:100 0.000