Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 1 07 Mar 2025, 15:46

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:44.556 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:18.011
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 1.277
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 32.610
When I start Tails from USB drive "old" with network unplugged 1:38.381
Then the boot device has safe access rights 3.631
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 3.611
After features/support/hooks.rb:100 0.007
Tags: @product
2:22.538
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:39.779
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 31.493
And I take note of which tps features are available 1.345
Then a Tails persistence partition exists on USB drive "old" 0.885
And I shutdown Tails and wait for the computer to power off 8.522
After features/support/hooks.rb:330 0.217
After features/support/hooks.rb:100 0.008
Tags: @product
3:9.092
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.977
Then Tails is running from USB drive "old" 0.449
And all tps features are active 1.878
When I write some files expected to persist 1.980
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.556
And all persistent directories from the old Tails version have safe access rights 2.580
And I take note of which tps features are available 0.418
And I shutdown Tails and wait for the computer to power off 4.504
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.334
After features/support/hooks.rb:330 0.116
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.937
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 10.219
And I log in to a new session 20.987
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.016
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.401
Then the running Tails is installed on USB drive "to_upgrade" 23.448
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 1.886
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.711
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:26.008
Then all tps features from the old Tails version are active 1.502
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.423
And the expected persistent files created with the old Tails version are present in the filesystem 1.582
And all persistent directories from the old Tails version have safe access rights 2.703
After features/support/hooks.rb:330 0.858
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:4.810
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.060
And no SquashFS delta is installed 0.275
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.065
And Tor is ready 24.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.241
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.851
Given I shutdown Tails and wait for the computer to power off 8.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.076
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.162
And the file system changes introduced in version 6.2~testoverlayfs are present 0.369
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.275
# 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.309
When the network is plugged 0.077
And Tor is ready 20.784
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.425
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.352
Given I shutdown Tails and wait for the computer to power off 4.408
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.389
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.263
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.076
And Tor is ready 16.518
Then the Upgrader considers the system as up-to-date 0.329
# 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.782
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.940
After features/support/hooks.rb:330 0.877
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
40.454
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.407
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.430
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.132
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 23.740
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.581
After features/support/hooks.rb:330 0.785
After features/support/hooks.rb:100 0.000