Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 24 29 Mar 2025, 16:30

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:4.190 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:10.451
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 27.887
When I start Tails from USB drive "old" with network unplugged 1:36.911
Then the boot device has safe access rights 3.359
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 6.993
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.021
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:36.085
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 31.852
And I take note of which tps features are available 1.482
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.266
After features/support/hooks.rb:330 0.203
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.641
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.891
Then Tails is running from USB drive "old" 1.116
And all tps features are active 1.840
When I write some files expected to persist 1.699
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.291
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 3.675
And I take note of which tps features are available 0.373
And I shutdown Tails and wait for the computer to power off 6.183
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.967
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.249
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.726
And I log in to a new session 18.435
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.627
And I plug USB drive "to_upgrade" 2.507
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.929
Then the running Tails is installed on USB drive "to_upgrade" 20.571
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.249
After features/support/hooks.rb:330 2.782
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.818
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.613
Then all tps features from the old Tails version are active 1.569
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.301
And the expected persistent files created with the old Tails version are present in the filesystem 1.415
And all persistent directories from the old Tails version have safe access rights 2.429
After features/support/hooks.rb:330 1.790
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:54.292
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.894
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.491
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.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.076
And Tor is ready 17.829
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.947
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.957
Given I shutdown Tails and wait for the computer to power off 8.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.662
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.008
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.250
When the network is plugged 0.093
And Tor is ready 18.342
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.701
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.641
Given I shutdown Tails and wait for the computer to power off 6.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.931
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.851
And the file system changes introduced in version 6.3~testoverlayfs are present 0.464
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.370
When the network is plugged 0.063
And Tor is ready 17.083
Then the Upgrader considers the system as up-to-date 0.309
# 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 15.870
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.414
After features/support/hooks.rb:330 0.724
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
32.714
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.472
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.540
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.120
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 14.725
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.740
After features/support/hooks.rb:330 1.033
After features/support/hooks.rb:100 0.000