Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 28 02 Apr 2025, 19:31

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:3.783 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:35.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.114
And I write an old version of the Tails USB image to disk "old" 37.947
When I start Tails from USB drive "old" with network unplugged 1:51.094
Then the boot device has safe access rights 3.822
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.346
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 3.520
After features/support/hooks.rb:100 0.012
Tags: @product
2:29.463
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login 1:40.851
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 36.621
And I take note of which tps features are available 1.550
Then a Tails persistence partition exists on USB drive "old" 0.942
And I shutdown Tails and wait for the computer to power off 8.923
After features/support/hooks.rb:330 0.252
After features/support/hooks.rb:100 0.009
Tags: @product
3:23.222
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.815
Then Tails is running from USB drive "old" 0.826
And all tps features are active 1.959
When I write some files expected to persist 1.976
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.594
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 4.059
And I take note of which tps features are available 3.758
And I shutdown Tails and wait for the computer to power off 6.528
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.096
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.714
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 without a persistent partition and stopped at Tails Greeter's login screen 10.412
And I log in to a new session 19.510
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.434
And I plug USB drive "to_upgrade" 2.508
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.810
Then the running Tails is installed on USB drive "to_upgrade" 23.037
And I unplug USB drive "to_upgrade" 0.474
And I unplug USB drive "__internal" 0.525
After features/support/hooks.rb:330 4.700
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.928
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.233
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:27.439
Then all tps features from the old Tails version are active 1.895
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 3.454
And the expected persistent files created with the old Tails version are present in the filesystem 1.807
And all persistent directories from the old Tails version have safe access rights 2.734
After features/support/hooks.rb:330 2.167
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:38.096
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 15.203
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.936
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.581
When the network is plugged 0.064
And Tor is ready 23.862
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.135
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.409
Given I shutdown Tails and wait for the computer to power off 11.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.428
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.330
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.405
# 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.290
When the network is plugged 0.081
And Tor is ready 16.058
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.281
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.877
Given I shutdown Tails and wait for the computer to power off 6.657
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.077
Then Tails is running version 6.3~testoverlayfs 0.050
And all tps features are active 3.050
And the file system changes introduced in version 6.3~testoverlayfs are present 0.610
And only the 6.3~testoverlayfs SquashFS delta is installed 0.105
# 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.379
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.506
When the network is plugged 0.113
And Tor is ready 20.055
Then the Upgrader considers the system as up-to-date 0.385
# 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 21.403
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.689
After features/support/hooks.rb:330 0.968
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
45.988
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 15.014
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.469
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.093
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 23.099
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.127
After features/support/hooks.rb:330 2.061
After features/support/hooks.rb:100 0.000