Project Number Date
test_Tails_ISO_20263-test-suite-without-spice 28 05 Apr 2025, 02:32

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 18:36.939 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
1:51.532
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.064
When I start Tails from USB drive "old" with network unplugged 1:15.495
Then the boot device has safe access rights 3.764
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 9.195
After features/support/hooks.rb:100 0.009
Tags: @product
2:1.485
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:19.366
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 30.912
And I take note of which tps features are available 1.565
Then a Tails persistence partition exists on USB drive "old" 0.688
And I shutdown Tails and wait for the computer to power off 8.471
After features/support/hooks.rb:330 0.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.840
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.672
Then Tails is running from USB drive "old" 0.308
And all tps features are active 2.242
When I write some files expected to persist 1.601
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 2.355
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 4.243
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.177
After features/support/hooks.rb:330 0.150
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.430
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.345
And I log in to a new session 20.322
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.312
And I plug USB drive "to_upgrade" 2.356
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.996
Then the running Tails is installed on USB drive "to_upgrade" 19.690
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 1.723
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.865
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.319
Then all tps features from the old Tails version are active 1.479
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.089
And the expected persistent files created with the old Tails version are present in the filesystem 1.292
And all persistent directories from the old Tails version have safe access rights 2.134
After features/support/hooks.rb:330 1.434
After features/support/hooks.rb:100 0.009
6:34.844
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 10.726
And no SquashFS delta is installed 0.200
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.947
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.072
And Tor is ready 20.570
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.820
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.191
Given I shutdown Tails and wait for the computer to power off 8.672
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.294
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.973
And the file system changes introduced in version 6.2~testoverlayfs are present 0.262
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.230
When the network is plugged 0.058
And Tor is ready 19.655
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.411
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.582
Given I shutdown Tails and wait for the computer to power off 4.370
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.357
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.812
And the file system changes introduced in version 6.3~testoverlayfs are present 0.469
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.092
And Tor is ready 21.216
Then the Upgrader considers the system as up-to-date 0.289
# 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 16.138
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.611
After features/support/hooks.rb:330 0.732
After features/support/hooks.rb:100 0.016
36.941
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 10.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.969
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 19.139
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.562
After features/support/hooks.rb:330 0.651
After features/support/hooks.rb:100 0.000