Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 7 12 Mar 2025, 17:32

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:6.219 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:20.007
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 33.828
When I start Tails from USB drive "old" with network unplugged 1:39.648
Then the boot device has safe access rights 3.539
And Tails is running from USB drive "old" 0.947
And there is no persistence partition on USB drive "old" 0.071
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.193
After features/support/hooks.rb:330 6.959
After features/support/hooks.rb:100 0.007
Tags: @product
2:22.338
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:39.137
Then Tails is running from USB drive "old" 0.451
And I create a persistent partition 31.926
And I take note of which tps features are available 1.382
Then a Tails persistence partition exists on USB drive "old" 0.919
And I shutdown Tails and wait for the computer to power off 8.328
After features/support/hooks.rb:330 0.209
After features/support/hooks.rb:100 0.010
Tags: @product
3:12.714
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.405
Then Tails is running from USB drive "old" 1.290
And all tps features are active 2.054
When I write some files expected to persist 3.055
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.274
And all persistence configuration files have safe access rights 0.469
And all persistent directories from the old Tails version have safe access rights 2.539
And I take note of which tps features are available 0.494
And I shutdown Tails and wait for the computer to power off 6.593
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.348
After features/support/hooks.rb:330 0.109
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.151
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 9.656
And I log in to a new session 23.709
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.858
And I plug USB drive "to_upgrade" 2.724
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.644
Then the running Tails is installed on USB drive "to_upgrade" 23.101
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:330 2.201
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.332
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.249
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.366
Then all tps features from the old Tails version are active 1.756
And Tails is running from USB drive "to_upgrade" 0.404
And the boot device has safe access rights 3.308
And the expected persistent files created with the old Tails version are present in the filesystem 1.783
And all persistent directories from the old Tails version have safe access rights 2.464
After features/support/hooks.rb:330 1.481
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:26.920
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 14.297
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.682
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.151
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.087
And Tor is ready 23.187
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.204
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.058
Given I shutdown Tails and wait for the computer to power off 11.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.313
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.209
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.259
# 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.297
When the network is plugged 0.078
And Tor is ready 18.804
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.549
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.015
Given I shutdown Tails and wait for the computer to power off 6.899
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.536
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.061
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.071
And Tor is ready 20.767
Then the Upgrader considers the system as up-to-date 0.353
# 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.936
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.047
After features/support/hooks.rb:330 1.034
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.754
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 12.233
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.671
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.118
And Tor is ready 19.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.526
After features/support/hooks.rb:330 1.225
After features/support/hooks.rb:100 0.000