Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 13 18 Mar 2025, 17:05

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:33.314 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:26.385
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.511
When I start Tails from USB drive "old" with network unplugged 1:46.948
Then the boot device has safe access rights 3.598
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:330 3.497
After features/support/hooks.rb:100 0.035
Tags: @product
2:34.255
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:39.318
Then Tails is running from USB drive "old" 0.498
And I create a persistent partition 42.999
And I take note of which tps features are available 2.096
Then a Tails persistence partition exists on USB drive "old" 0.797
And I shutdown Tails and wait for the computer to power off 8.346
After features/support/hooks.rb:330 0.215
After features/support/hooks.rb:100 0.008
Tags: @product
3:8.326
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 "old" with network unplugged and I login with persistence enabled 2:31.059
Then Tails is running from USB drive "old" 0.350
And all tps features are active 1.841
When I write some files expected to persist 1.756
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 2.660
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.627
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.784
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.047
Tags: @product
2:47.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.516
And I log in to a new session 20.027
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.898
And I plug USB drive "to_upgrade" 2.538
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.263
Then the running Tails is installed on USB drive "to_upgrade" 26.040
And I unplug USB drive "to_upgrade" 0.259
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 1.877
After features/support/hooks.rb:100 0.000
Tags: @product
2:40.197
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.242
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:29.649
Then all tps features from the old Tails version are active 2.024
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.254
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 3.244
After features/support/hooks.rb:330 1.685
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
8:20.566
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 35.984
And no SquashFS delta is installed 0.283
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.095
And Tor is ready 21.006
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.135
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.391
Given I shutdown Tails and wait for the computer to power off 9.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.888
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.426
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.255
# 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.286
When the network is plugged 0.087
And Tor is ready 22.299
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.705
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.094
Given I shutdown Tails and wait for the computer to power off 8.661
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:51.861
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.561
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.533
When the network is plugged 0.083
And Tor is ready 18.838
Then the Upgrader considers the system as up-to-date 0.344
# 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.685
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.087
After features/support/hooks.rb:330 0.811
After features/support/hooks.rb:100 0.081
Tags: @product @automatic_upgrade
35.819
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.443
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the signing key used by the Upgrader is outdated 0.134
But a current signing key is available on our website 0.000
When the network is plugged 0.139
And Tor is ready 17.788
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.794
After features/support/hooks.rb:330 1.393
After features/support/hooks.rb:100 0.000