Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 6 11 Mar 2025, 18:28

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 23:43.491 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:38.667
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 37.955
When I start Tails from USB drive "old" with network unplugged 1:54.425
Then the boot device has safe access rights 3.859
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 3.926
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.218
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.854
And I start Tails from USB drive "old" with network unplugged and I login 1:43.850
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 32.970
And I take note of which tps features are available 1.717
Then a Tails persistence partition exists on USB drive "old" 0.858
And I shutdown Tails and wait for the computer to power off 8.602
After features/support/hooks.rb:330 0.195
After features/support/hooks.rb:100 0.008
Tags: @product
3:36.992
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:57.203
Then Tails is running from USB drive "old" 0.584
And all tps features are active 2.459
When I write some files expected to persist 2.052
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.292
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.728
And I take note of which tps features are available 0.652
And I shutdown Tails and wait for the computer to power off 4.407
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.922
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.984
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 16.575
And I log in to a new session 21.175
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.054
And I plug USB drive "to_upgrade" 2.512
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.791
Then the running Tails is installed on USB drive "to_upgrade" 25.939
And I unplug USB drive "to_upgrade" 0.565
And I unplug USB drive "__internal" 0.370
After features/support/hooks.rb:330 3.523
After features/support/hooks.rb:100 0.000
Tags: @product
2:46.372
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.269
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:35.151
Then all tps features from the old Tails version are active 2.152
And Tails is running from USB drive "to_upgrade" 0.387
And the boot device has safe access rights 3.858
And the expected persistent files created with the old Tails version are present in the filesystem 1.726
And all persistent directories from the old Tails version have safe access rights 2.827
After features/support/hooks.rb:330 1.402
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
8:37.354
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 41.265
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.606
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.441
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.530
When the network is plugged 0.079
And Tor is ready 51.246
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.782
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.735
Given I shutdown Tails and wait for the computer to power off 9.299
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:35.618
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.709
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.274
# 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.368
When the network is plugged 0.091
And Tor is ready 20.414
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.750
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.820
Given I shutdown Tails and wait for the computer to power off 6.514
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:33.317
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.324
And the file system changes introduced in version 6.3~testoverlayfs are present 0.523
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.265
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.317
When the network is plugged 0.100
And Tor is ready 17.165
Then the Upgrader considers the system as up-to-date 10.888
# 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.091
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.069
After features/support/hooks.rb:330 0.817
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
41.900
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.363
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.784
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
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.078
And Tor is ready 22.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.157
After features/support/hooks.rb:330 0.749
After features/support/hooks.rb:100 0.000