Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 16 21 Mar 2025, 16:23

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 20:7.464 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:12.961
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.011
When I start Tails from USB drive "old" with network unplugged 1:36.427
Then the boot device has safe access rights 3.266
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 3.466
After features/support/hooks.rb:100 0.008
Tags: @product
2:20.746
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:36.393
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 33.547
And I take note of which tps features are available 1.269
Then a Tails persistence partition exists on USB drive "old" 0.828
And I shutdown Tails and wait for the computer to power off 8.225
After features/support/hooks.rb:330 0.181
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.078
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.043
Then Tails is running from USB drive "old" 0.609
And all tps features are active 1.833
When I write some files expected to persist 1.675
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.533
And all persistent directories from the old Tails version have safe access rights 3.050
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.647
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.835
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.017
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.555
And I log in to a new session 17.117
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.545
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.346
Then the running Tails is installed on USB drive "to_upgrade" 18.621
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 1.685
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.848
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:27.058
Then all tps features from the old Tails version are active 1.710
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.064
And the expected persistent files created with the old Tails version are present in the filesystem 1.342
And all persistent directories from the old Tails version have safe access rights 2.183
After features/support/hooks.rb:330 0.925
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:53.029
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.113
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.689
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.548
When the network is plugged 0.070
And Tor is ready 20.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.398
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.201
Given I shutdown Tails and wait for the computer to power off 8.413
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.166
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.088
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.289
When the network is plugged 0.071
And Tor is ready 18.549
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.255
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.576
Given I shutdown Tails and wait for the computer to power off 4.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.379
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.926
And the file system changes introduced in version 6.3~testoverlayfs are present 0.430
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.259
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.070
And Tor is ready 19.606
Then the Upgrader considers the system as up-to-date 0.288
# 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 14.770
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.914
After features/support/hooks.rb:330 0.849
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.781
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 9.675
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.675
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 20.949
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.263
After features/support/hooks.rb:330 0.668
After features/support/hooks.rb:100 0.000