Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 21 26 Mar 2025, 18:13

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:27.524 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
3:15.733
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.262
And I create a 7200 MiB disk named "old" 0.072
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 1:15.152
When I start Tails from USB drive "old" with network unplugged 1:54.754
Then the boot device has safe access rights 3.413
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:330 3.823
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 1.373
And I start Tails from USB drive "old" with network unplugged and I login 1:42.678
Then Tails is running from USB drive "old" 0.416
And I create a persistent partition 33.358
And I take note of which tps features are available 1.517
Then a Tails persistence partition exists on USB drive "old" 0.851
And I shutdown Tails and wait for the computer to power off 8.992
After features/support/hooks.rb:330 0.296
After features/support/hooks.rb:100 0.011
Tags: @product
3:20.731
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:39.222
Then Tails is running from USB drive "old" 0.502
And all tps features are active 2.205
When I write some files expected to persist 2.072
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.353
And all persistence configuration files have safe access rights 0.488
And all persistent directories from the old Tails version have safe access rights 2.998
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 6.617
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.526
After features/support/hooks.rb:330 0.142
After features/support/hooks.rb:100 0.011
Tags: @product
2:44.569
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 9.950
And I log in to a new session 20.205
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.684
And I plug USB drive "to_upgrade" 2.679
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.565
Then the running Tails is installed on USB drive "to_upgrade" 29.954
And I unplug USB drive "to_upgrade" 0.304
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 2.614
After features/support/hooks.rb:100 0.000
Tags: @product
3:13.796
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 1.000
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:59.063
Then all tps features from the old Tails version are active 4.237
And Tails is running from USB drive "to_upgrade" 0.659
And the boot device has safe access rights 4.294
And the expected persistent files created with the old Tails version are present in the filesystem 1.548
And all persistent directories from the old Tails version have safe access rights 2.993
After features/support/hooks.rb:330 1.660
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:39.702
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 24.605
And no SquashFS delta is installed 0.325
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.367
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.483
When the network is plugged 0.130
And Tor is ready 24.385
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.329
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.136
Given I shutdown Tails and wait for the computer to power off 9.735
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.076
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.464
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.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.326
When the network is plugged 0.076
And Tor is ready 21.475
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.070
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.612
Given I shutdown Tails and wait for the computer to power off 7.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.588
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.130
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.276
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.406
When the network is plugged 0.068
And Tor is ready 18.169
Then the Upgrader considers the system as up-to-date 0.484
# 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 17.408
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.765
After features/support/hooks.rb:330 0.743
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
43.801
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 11.404
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.090
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 23.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.124
After features/support/hooks.rb:330 0.911
After features/support/hooks.rb:100 0.000