Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 34 09 Apr 2025, 17:11

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 23:3.650 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:21.120
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 31.557
When I start Tails from USB drive "old" with network unplugged 1:42.942
Then the boot device has safe access rights 4.170
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:330 1.137
After features/support/hooks.rb:100 0.018
Tags: @product
2:31.659
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login 1:42.587
Then Tails is running from USB drive "old" 0.626
And I create a persistent partition 36.169
And I take note of which tps features are available 1.891
Then a Tails persistence partition exists on USB drive "old" 0.964
And I shutdown Tails and wait for the computer to power off 9.192
After features/support/hooks.rb:330 0.227
After features/support/hooks.rb:100 0.015
Tags: @product
3:33.158
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:49.266
Then Tails is running from USB drive "old" 0.471
And all tps features are active 2.654
When I write some files expected to persist 1.895
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.298
And all persistence configuration files have safe access rights 0.454
And all persistent directories from the old Tails version have safe access rights 2.885
And I take note of which tps features are available 0.672
And I shutdown Tails and wait for the computer to power off 6.548
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.768
After features/support/hooks.rb:330 0.166
After features/support/hooks.rb:100 0.015
Tags: @product
3:2.491
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 20.189
And I log in to a new session 24.351
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.471
And I plug USB drive "to_upgrade" 2.683
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.979
Then the running Tails is installed on USB drive "to_upgrade" 28.745
And I unplug USB drive "to_upgrade" 0.474
And I unplug USB drive "__internal" 0.595
After features/support/hooks.rb:330 1.405
After features/support/hooks.rb:100 0.000
Tags: @product
2:39.706
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 1.312
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:27.750
Then all tps features from the old Tails version are active 1.846
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 4.127
And the expected persistent files created with the old Tails version are present in the filesystem 1.564
And all persistent directories from the old Tails version have safe access rights 2.715
After features/support/hooks.rb:330 1.271
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:17.612
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 35.606
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.367
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.532
When the network is plugged 0.092
And Tor is ready 18.658
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.466
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.452
Given I shutdown Tails and wait for the computer to power off 10.997
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:32.434
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.679
And the file system changes introduced in version 6.2~testoverlayfs are present 0.371
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.353
When the network is plugged 0.106
And Tor is ready 21.532
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.038
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.402
Given I shutdown Tails and wait for the computer to power off 6.838
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:34.737
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 3.038
And the file system changes introduced in version 6.3~testoverlayfs are present 0.612
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.345
When the network is plugged 0.126
And Tor is ready 21.341
Then the Upgrader considers the system as up-to-date 0.338
# 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 21.586
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.065
After features/support/hooks.rb:330 0.899
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
37.901
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 with a persistent partition enabled and logged in 11.479
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.448
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.089
But a current signing key is available on our website 0.000
When the network is plugged 0.208
And Tor is ready 19.824
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.776
After features/support/hooks.rb:330 1.998
After features/support/hooks.rb:100 0.000