Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 17 22 Mar 2025, 16:25

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:56.726 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:17.173
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.270
When I start Tails from USB drive "old" with network unplugged 1:41.466
Then the boot device has safe access rights 3.265
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 6.993
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.403
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:37.407
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 32.671
And I take note of which tps features are available 1.433
Then a Tails persistence partition exists on USB drive "old" 0.726
And I shutdown Tails and wait for the computer to power off 8.677
After features/support/hooks.rb:330 0.175
After features/support/hooks.rb:100 0.009
Tags: @product
3:4.635
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.794
Then Tails is running from USB drive "old" 0.399
And all tps features are active 1.810
When I write some files expected to persist 2.628
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.231
And I take note of which tps features are available 0.388
And I shutdown Tails and wait for the computer to power off 4.678
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.954
After features/support/hooks.rb:330 0.090
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.782
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 10.076
And I log in to a new session 18.577
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.040
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.509
Then the running Tails is installed on USB drive "to_upgrade" 16.678
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:330 2.859
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.721
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.808
Then all tps features from the old Tails version are active 1.666
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 2.981
And the expected persistent files created with the old Tails version are present in the filesystem 1.420
And all persistent directories from the old Tails version have safe access rights 2.336
After features/support/hooks.rb:330 1.247
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:44.741
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 11.545
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.507
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.058
And Tor is ready 16.994
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.876
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.299
Given I shutdown Tails and wait for the computer to power off 8.456
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.543
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.052
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.287
# 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.290
When the network is plugged 0.063
And Tor is ready 17.753
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.253
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.876
Given I shutdown Tails and wait for the computer to power off 4.122
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.778
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.909
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.297
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.066
And Tor is ready 18.026
Then the Upgrader considers the system as up-to-date 0.318
# 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 15.267
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.967
After features/support/hooks.rb:330 0.737
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
33.267
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 9.439
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 17.112
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.245
After features/support/hooks.rb:330 1.247
After features/support/hooks.rb:100 0.000