Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 14 19 Mar 2025, 16:55

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 22:48.369 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:23.823
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 32.950
When I start Tails from USB drive "old" with network unplugged 1:44.714
Then the boot device has safe access rights 3.667
And Tails is running from USB drive "old" 0.398
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.358
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:330 3.550
After features/support/hooks.rb:100 0.065
Tags: @product
2:29.779
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:44.398
Then Tails is running from USB drive "old" 0.393
And I create a persistent partition 33.540
And I take note of which tps features are available 1.604
Then a Tails persistence partition exists on USB drive "old" 0.936
And I shutdown Tails and wait for the computer to power off 8.709
After features/support/hooks.rb:330 0.225
After features/support/hooks.rb:100 0.009
Tags: @product
3:23.426
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:42.306
Then Tails is running from USB drive "old" 0.479
And all tps features are active 2.424
When I write some files expected to persist 2.254
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 2.683
And I take note of which tps features are available 0.557
And I shutdown Tails and wait for the computer to power off 6.476
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.309
After features/support/hooks.rb:330 0.118
After features/support/hooks.rb:100 0.011
Tags: @product
2:37.614
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 11.336
And I log in to a new session 20.919
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.503
And I plug USB drive "to_upgrade" 2.829
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.685
Then the running Tails is installed on USB drive "to_upgrade" 22.854
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.257
After features/support/hooks.rb:330 1.843
After features/support/hooks.rb:100 0.000
Tags: @product
2:57.054
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:46.213
Then all tps features from the old Tails version are active 1.894
And Tails is running from USB drive "to_upgrade" 0.397
And the boot device has safe access rights 3.924
And the expected persistent files created with the old Tails version are present in the filesystem 1.739
And all persistent directories from the old Tails version have safe access rights 2.661
After features/support/hooks.rb:330 1.635
After features/support/hooks.rb:100 0.008
8:8.297
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 14.183
And no SquashFS delta is installed 0.411
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.810
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.075
And Tor is ready 31.020
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.530
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.770
Given I shutdown Tails and wait for the computer to power off 11.035
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:32.664
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.564
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
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.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.350
When the network is plugged 0.084
And Tor is ready 17.911
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.205
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.465
Given I shutdown Tails and wait for the computer to power off 4.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.215
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.408
And the file system changes introduced in version 6.3~testoverlayfs are present 0.590
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.072
And Tor is ready 47.783
Then the Upgrader considers the system as up-to-date 0.346
# 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.468
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.531
After features/support/hooks.rb:330 0.854
After features/support/hooks.rb:100 0.025
48.373
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 18.838
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.517
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 23.241
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.551
After features/support/hooks.rb:330 1.773
After features/support/hooks.rb:100 0.000