Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 19 24 Mar 2025, 16: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:22.689 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:14.910
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.163
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 30.666
When I start Tails from USB drive "old" with network unplugged 1:38.601
Then the boot device has safe access rights 3.410
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 8.748
After features/support/hooks.rb:100 0.007
Tags: @product
2:21.103
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login 1:38.833
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 31.376
And I take note of which tps features are available 1.378
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.208
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.007
Tags: @product
3:2.331
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.358
Then Tails is running from USB drive "old" 0.772
And all tps features are active 1.877
When I write some files expected to persist 1.750
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 3.223
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 4.865
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.252
After features/support/hooks.rb:330 0.133
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.864
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.069
And I log in to a new session 17.734
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.717
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.852
Then the running Tails is installed on USB drive "to_upgrade" 19.654
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:330 1.845
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.377
Then all tps features from the old Tails version are active 1.797
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.189
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.427
After features/support/hooks.rb:330 1.572
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:9.189
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.928
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.392
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.384
When the network is plugged 0.066
And Tor is ready 23.706
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.450
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.660
Given I shutdown Tails and wait for the computer to power off 8.644
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.672
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.087
And the file system changes introduced in version 6.2~testoverlayfs are present 0.352
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.256
# 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.368
When the network is plugged 0.082
And Tor is ready 20.850
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.192
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.949
Given I shutdown Tails and wait for the computer to power off 4.248
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.258
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.184
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.280
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.319
When the network is plugged 0.063
And Tor is ready 16.460
Then the Upgrader considers the system as up-to-date 0.331
# 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.691
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.136
After features/support/hooks.rb:330 0.749
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.510
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.936
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.147
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 19.458
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.367
After features/support/hooks.rb:330 0.720
After features/support/hooks.rb:100 0.000