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

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:11.984 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:33.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.731
When I start Tails from USB drive "old" with network unplugged 1:57.437
Then the boot device has safe access rights 3.321
And Tails is running from USB drive "old" 0.434
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:330 3.786
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.602
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login 1:44.079
Then Tails is running from USB drive "old" 0.439
And I create a persistent partition 32.747
And I take note of which tps features are available 1.541
Then a Tails persistence partition exists on USB drive "old" 0.871
And I shutdown Tails and wait for the computer to power off 8.678
After features/support/hooks.rb:330 0.212
After features/support/hooks.rb:100 0.010
Tags: @product
3:10.624
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.281
Then Tails is running from USB drive "old" 0.799
And all tps features are active 2.654
When I write some files expected to persist 1.797
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.517
And all persistent directories from the old Tails version have safe access rights 2.464
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 6.397
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.771
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.914
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 10.145
And I log in to a new session 17.869
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.647
And I plug USB drive "to_upgrade" 2.509
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.387
Then the running Tails is installed on USB drive "to_upgrade" 18.871
And I unplug USB drive "to_upgrade" 0.263
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 2.144
After features/support/hooks.rb:100 0.000
Tags: @product
2:38.456
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.243
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:27.293
Then all tps features from the old Tails version are active 2.189
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 3.957
And the expected persistent files created with the old Tails version are present in the filesystem 1.662
And all persistent directories from the old Tails version have safe access rights 2.726
After features/support/hooks.rb:330 1.429
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:12.577
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.225
And no SquashFS delta is installed 0.256
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.619
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.420
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.507
When the network is plugged 0.073
And Tor is ready 24.242
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.667
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.988
Given I shutdown Tails and wait for the computer to power off 11.721
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.340
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.410
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.449
When the network is plugged 0.073
And Tor is ready 19.776
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.245
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.732
Given I shutdown Tails and wait for the computer to power off 4.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.929
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.081
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.268
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.364
When the network is plugged 0.107
And Tor is ready 18.720
Then the Upgrader considers the system as up-to-date 0.299
# 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.199
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.249
After features/support/hooks.rb:330 0.845
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
37.860
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.142
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.705
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.139
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 21.596
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.137
After features/support/hooks.rb:330 1.016
After features/support/hooks.rb:100 0.000