Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 30 04 Apr 2025, 16:36

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 20:42.708 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:22.669
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.299
When I start Tails from USB drive "old" with network unplugged 1:44.914
Then the boot device has safe access rights 4.128
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:330 6.928
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.001
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login 1:35.325
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 31.591
And I take note of which tps features are available 1.683
Then a Tails persistence partition exists on USB drive "old" 0.712
And I shutdown Tails and wait for the computer to power off 8.217
After features/support/hooks.rb:330 0.206
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.479
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.230
Then Tails is running from USB drive "old" 0.332
And all tps features are active 1.902
When I write some files expected to persist 1.992
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.342
And I take note of which tps features are available 0.389
And I shutdown Tails and wait for the computer to power off 4.400
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.078
After features/support/hooks.rb:330 0.118
After features/support/hooks.rb:100 0.011
Tags: @product
2:29.941
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.776
And I log in to a new session 18.905
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.614
And I plug USB drive "to_upgrade" 2.704
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.558
Then the running Tails is installed on USB drive "to_upgrade" 22.919
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:330 1.052
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.888
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.889
Then all tps features from the old Tails version are active 1.476
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.132
And the expected persistent files created with the old Tails version are present in the filesystem 1.502
And all persistent directories from the old Tails version have safe access rights 2.374
After features/support/hooks.rb:330 1.428
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:18.864
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.878
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.684
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.078
And Tor is ready 19.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.868
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.941
Given I shutdown Tails and wait for the computer to power off 8.638
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.869
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.040
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
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.329
# 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.314
When the network is plugged 0.099
And Tor is ready 20.701
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.671
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.936
Given I shutdown Tails and wait for the computer to power off 6.487
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.817
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.896
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.063
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.098
And Tor is ready 19.922
Then the Upgrader considers the system as up-to-date 11.188
# 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 17.378
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.945
After features/support/hooks.rb:330 0.767
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.862
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 10.253
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 21.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.418
After features/support/hooks.rb:330 0.700
After features/support/hooks.rb:100 0.000