Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 9 14 Mar 2025, 16:47

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 21:28.868 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:23.613
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 28.853
When I start Tails from USB drive "old" with network unplugged 1:48.790
Then the boot device has safe access rights 3.671
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 6.745
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.193
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login 1:50.188
Then Tails is running from USB drive "old" 0.393
And I create a persistent partition 31.376
And I take note of which tps features are available 1.537
Then a Tails persistence partition exists on USB drive "old" 0.799
And I shutdown Tails and wait for the computer to power off 8.633
After features/support/hooks.rb:330 0.213
After features/support/hooks.rb:100 0.008
Tags: @product
3:11.073
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.981
Then Tails is running from USB drive "old" 0.488
And all tps features are active 2.220
When I write some files expected to persist 2.016
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.461
And I take note of which tps features are available 0.534
And I shutdown Tails and wait for the computer to power off 4.346
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.166
After features/support/hooks.rb:330 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.878
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.960
And I log in to a new session 20.383
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.495
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.135
Then the running Tails is installed on USB drive "to_upgrade" 25.025
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 1.681
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.521
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.476
Then all tps features from the old Tails version are active 1.994
And Tails is running from USB drive "to_upgrade" 0.492
And the boot device has safe access rights 4.063
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.823
After features/support/hooks.rb:330 1.813
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:25.022
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.390
And no SquashFS delta is installed 0.291
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.474
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.123
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.524
When the network is plugged 0.088
And Tor is ready 24.363
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.446
Given I shutdown Tails and wait for the computer to power off 10.802
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.901
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.554
And the file system changes introduced in version 6.2~testoverlayfs are present 0.459
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.348
When the network is plugged 0.149
And Tor is ready 45.833
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.604
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.082
Given I shutdown Tails and wait for the computer to power off 4.223
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.729
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.284
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.275
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.084
And Tor is ready 18.433
Then the Upgrader considers the system as up-to-date 0.303
# 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 15.392
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.972
After features/support/hooks.rb:330 0.998
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
48.564
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.004
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.454
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 20.820
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.981
After features/support/hooks.rb:330 0.801
After features/support/hooks.rb:100 0.000