Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 22 27 Mar 2025, 19:50

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 22:39.245 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:27.252
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 29.799
When I start Tails from USB drive "old" with network unplugged 1:50.095
Then the boot device has safe access rights 4.026
And Tails is running from USB drive "old" 0.469
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.151
And udev-watchdog is monitoring the correct device 0.511
And I unplug USB drive "old" 0.781
After features/support/hooks.rb:330 3.607
After features/support/hooks.rb:100 0.016
Tags: @product
2:31.894
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.287
And I start Tails from USB drive "old" with network unplugged and I login 1:42.040
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 36.006
And I take note of which tps features are available 3.850
Then a Tails persistence partition exists on USB drive "old" 0.918
And I shutdown Tails and wait for the computer to power off 8.416
After features/support/hooks.rb:330 0.241
After features/support/hooks.rb:100 0.007
Tags: @product
3:19.953
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 2.002
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.384
Then Tails is running from USB drive "old" 0.378
And all tps features are active 2.284
When I write some files expected to persist 1.712
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.309
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.594
And I take note of which tps features are available 0.893
And I shutdown Tails and wait for the computer to power off 6.673
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.327
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.007
Tags: @product
2:55.960
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 19.571
And I log in to a new session 21.623
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.738
And I plug USB drive "to_upgrade" 2.511
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.043
Then the running Tails is installed on USB drive "to_upgrade" 29.969
And I unplug USB drive "to_upgrade" 0.284
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 0.947
After features/support/hooks.rb:100 0.000
Tags: @product
2:51.216
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.668
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:40.149
Then all tps features from the old Tails version are active 2.040
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.939
And the expected persistent files created with the old Tails version are present in the filesystem 1.434
And all persistent directories from the old Tails version have safe access rights 2.663
After features/support/hooks.rb:330 2.102
After features/support/hooks.rb:100 0.007
7:54.887
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.262
And no SquashFS delta is installed 0.590
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.525
When the network is plugged 0.087
And Tor is ready 23.069
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.659
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.342
Given I shutdown Tails and wait for the computer to power off 8.977
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.893
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.642
And the file system changes introduced in version 6.2~testoverlayfs are present 0.428
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.795
When the network is plugged 0.259
And Tor is ready 49.147
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.678
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.675
Given I shutdown Tails and wait for the computer to power off 6.362
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.466
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 4.719
And the file system changes introduced in version 6.3~testoverlayfs are present 0.602
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.250
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.338
When the network is plugged 0.440
And Tor is ready 20.168
Then the Upgrader considers the system as up-to-date 0.306
# 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.016
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.939
After features/support/hooks.rb:330 1.057
After features/support/hooks.rb:100 0.011
38.080
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.720
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.777
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.263
And Tor is ready 20.105
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.074
After features/support/hooks.rb:330 1.442
After features/support/hooks.rb:100 0.000