Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 11 16 Mar 2025, 16:21

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 19:58.689 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:13.581
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.380
When I start Tails from USB drive "old" with network unplugged 1:38.792
Then the boot device has safe access rights 3.183
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 3.525
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.673
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:34.972
Then Tails is running from USB drive "old" 0.399
And I create a persistent partition 32.351
And I take note of which tps features are available 1.458
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 8.555
After features/support/hooks.rb:330 0.172
After features/support/hooks.rb:100 0.009
Tags: @product
3:10.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:34.422
Then Tails is running from USB drive "old" 0.386
And all tps features are active 2.143
When I write some files expected to persist 1.584
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
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.359
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.216
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.921
After features/support/hooks.rb:330 0.115
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.267
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.689
And I log in to a new session 18.794
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.453
And I plug USB drive "to_upgrade" 2.516
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.167
Then the running Tails is installed on USB drive "to_upgrade" 22.238
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 1.839
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.840
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.913
Then all tps features from the old Tails version are active 1.544
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 3.014
And the expected persistent files created with the old Tails version are present in the filesystem 1.574
And all persistent directories from the old Tails version have safe access rights 2.321
After features/support/hooks.rb:330 1.055
After features/support/hooks.rb:100 0.009
6:53.440
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 with a persistent partition enabled and logged in 12.013
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.597
When the network is plugged 0.069
And Tor is ready 28.054
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.574
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.497
Given I shutdown Tails and wait for the computer to power off 8.652
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.074
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.895
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.275
# 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.277
When the network is plugged 0.066
And Tor is ready 19.154
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.973
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.655
Given I shutdown Tails and wait for the computer to power off 4.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.391
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.019
And the file system changes introduced in version 6.3~testoverlayfs are present 0.451
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.267
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.363
When the network is plugged 0.077
And Tor is ready 19.503
Then the Upgrader considers the system as up-to-date 0.291
# 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 14.583
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.091
After features/support/hooks.rb:330 0.676
After features/support/hooks.rb:100 0.018
31.596
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 with a persistent partition enabled and logged in 10.036
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
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.069
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 15.925
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.041
After features/support/hooks.rb:330 1.300
After features/support/hooks.rb:100 0.000