Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 23 28 Mar 2025, 16: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 20:41.726 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:17.560
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.918
When I start Tails from USB drive "old" with network unplugged 1:40.097
Then the boot device has safe access rights 3.307
And Tails is running from USB drive "old" 0.288
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 7.116
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.992
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:38.391
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 30.679
And I take note of which tps features are available 1.298
Then a Tails persistence partition exists on USB drive "old" 0.791
And I shutdown Tails and wait for the computer to power off 8.315
After features/support/hooks.rb:330 0.234
After features/support/hooks.rb:100 0.009
Tags: @product
3:14.514
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:37.569
Then Tails is running from USB drive "old" 0.361
And all tps features are active 1.836
When I write some files expected to persist 1.839
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.471
And I take note of which tps features are available 1.102
And I shutdown Tails and wait for the computer to power off 4.297
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.251
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.018
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 10.029
And I log in to a new session 19.550
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.687
And I plug USB drive "to_upgrade" 2.599
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.621
Then the running Tails is installed on USB drive "to_upgrade" 24.067
And I unplug USB drive "to_upgrade" 0.246
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 0.822
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.979
Then all tps features from the old Tails version are active 1.691
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.544
And the expected persistent files created with the old Tails version are present in the filesystem 1.505
And all persistent directories from the old Tails version have safe access rights 2.800
After features/support/hooks.rb:330 1.371
After features/support/hooks.rb:100 0.009
7:13.458
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 11.784
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.448
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.066
And Tor is ready 20.987
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.176
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.485
Given I shutdown Tails and wait for the computer to power off 8.885
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.033
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.059
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
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.278
# 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.277
When the network is plugged 0.074
And Tor is ready 19.158
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.550
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.776
Given I shutdown Tails and wait for the computer to power off 4.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.683
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.128
And the file system changes introduced in version 6.3~testoverlayfs are present 0.526
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.084
And Tor is ready 20.375
Then the Upgrader considers the system as up-to-date 0.321
# 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.691
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.272
After features/support/hooks.rb:330 0.717
After features/support/hooks.rb:100 0.019
34.100
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 10.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 16.960
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.431
After features/support/hooks.rb:330 0.807
After features/support/hooks.rb:100 0.000