Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 15 20 Mar 2025, 16:27

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.815 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:21.379
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.986
When I start Tails from USB drive "old" with network unplugged 1:42.665
Then the boot device has safe access rights 3.345
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.067
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.211
After features/support/hooks.rb:330 3.750
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.711
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:45.335
Then Tails is running from USB drive "old" 0.410
And I create a persistent partition 32.960
And I take note of which tps features are available 1.542
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 8.433
After features/support/hooks.rb:330 0.193
After features/support/hooks.rb:100 0.008
Tags: @product
3:9.943
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.167
Then Tails is running from USB drive "old" 0.347
And all tps features are active 2.315
When I write some files expected to persist 1.840
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.451
And all persistent directories from the old Tails version have safe access rights 2.647
And I take note of which tps features are available 0.406
And I shutdown Tails and wait for the computer to power off 4.537
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.813
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.695
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.176
And I log in to a new session 18.653
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.944
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.934
Then the running Tails is installed on USB drive "to_upgrade" 21.081
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:330 1.697
After features/support/hooks.rb:100 0.000
Tags: @product
2:45.816
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.232
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:35.827
Then all tps features from the old Tails version are active 1.598
And Tails is running from USB drive "to_upgrade" 0.401
And the boot device has safe access rights 3.855
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.446
After features/support/hooks.rb:330 1.775
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:17.574
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 11.307
And no SquashFS delta is installed 0.190
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.670
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.060
And Tor is ready 23.919
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.294
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.442
Given I shutdown Tails and wait for the computer to power off 8.784
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.149
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.549
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.267
# 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.284
When the network is plugged 0.078
And Tor is ready 19.753
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.451
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.847
Given I shutdown Tails and wait for the computer to power off 4.470
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:30.152
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.177
And the file system changes introduced in version 6.3~testoverlayfs are present 0.472
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.069
And Tor is ready 20.840
Then the Upgrader considers the system as up-to-date 0.331
# 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.394
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.545
After features/support/hooks.rb:330 0.816
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.693
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 9.698
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.539
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.218
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 20.304
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.781
After features/support/hooks.rb:330 0.698
After features/support/hooks.rb:100 0.000