Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 5 10 Mar 2025, 17:39

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 21:54.068 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:27.847
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.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.466
When I start Tails from USB drive "old" with network unplugged 1:50.034
Then the boot device has safe access rights 3.867
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.358
And I unplug USB drive "old" 0.279
After features/support/hooks.rb:330 3.780
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.752
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 1.406
And I start Tails from USB drive "old" with network unplugged and I login 1:42.380
Then Tails is running from USB drive "old" 0.449
And I create a persistent partition 36.771
And I take note of which tps features are available 2.139
Then a Tails persistence partition exists on USB drive "old" 1.123
And I shutdown Tails and wait for the computer to power off 9.481
After features/support/hooks.rb:330 0.270
After features/support/hooks.rb:100 0.012
Tags: @product
3:25.614
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.871
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:42.928
Then Tails is running from USB drive "old" 0.377
And all tps features are active 2.386
When I write some files expected to persist 2.033
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.601
And all persistent directories from the old Tails version have safe access rights 2.793
And I take note of which tps features are available 0.596
And I shutdown Tails and wait for the computer to power off 6.716
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.072
After features/support/hooks.rb:330 0.173
After features/support/hooks.rb:100 0.013
Tags: @product
2:37.101
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 without a persistent partition and stopped at Tails Greeter's login screen 11.971
And I log in to a new session 21.645
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.591
And I plug USB drive "to_upgrade" 2.504
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.013
Then the running Tails is installed on USB drive "to_upgrade" 24.880
And I unplug USB drive "to_upgrade" 0.275
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 2.166
After features/support/hooks.rb:100 0.000
Tags: @product
2:36.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.248
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:26.537
Then all tps features from the old Tails version are active 1.629
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.664
And the expected persistent files created with the old Tails version are present in the filesystem 1.459
And all persistent directories from the old Tails version have safe access rights 2.399
After features/support/hooks.rb:330 1.164
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
7:14.372
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.362
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.453
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.374
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.071
And Tor is ready 24.128
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.146
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.267
Given I shutdown Tails and wait for the computer to power off 9.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.336
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.299
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.268
# 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.258
When the network is plugged 0.098
And Tor is ready 17.697
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.182
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.281
Given I shutdown Tails and wait for the computer to power off 4.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.199
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.274
And the file system changes introduced in version 6.3~testoverlayfs are present 0.469
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.078
And Tor is ready 17.639
Then the Upgrader considers the system as up-to-date 0.332
# 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.636
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.978
After features/support/hooks.rb:330 0.794
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
59.092
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.200
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.742
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.107
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 47.300
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.612
After features/support/hooks.rb:330 0.698
After features/support/hooks.rb:100 0.000