Project Number Date
test_Tails_ISO_stable 5980 02 Dec 2025, 13:12

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 16:17.679 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:9.162
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 33.708
When I start Tails from USB drive "old" with network unplugged 1:28.342
Then the boot device has safe access rights 4.720
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.260
After features/support/hooks.rb:331 3.888
After features/support/hooks.rb:100 0.039
Tags: @product
2:17.082
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:32.470
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 34.172
And I take note of which tps features are available 1.579
Then a Tails persistence partition exists on USB drive "old" 0.992
And I shutdown Tails and wait for the computer to power off 7.389
After features/support/hooks.rb:331 0.541
After features/support/hooks.rb:100 0.012
Tags: @product
2:16.061
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.955
Then Tails is running from USB drive "old" 0.814
And all tps features are active 2.097
When I write some files expected to persist 1.634
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.342
And all persistent directories from the old Tails version have safe access rights 2.151
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 8.057
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 20.126
After features/support/hooks.rb:331 0.657
After features/support/hooks.rb:100 0.011
Tags: @product
2:43.613
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 12.925
And I log in to a new session 17.067
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.917
And I plug USB drive "to_upgrade" 2.553
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.916
Then the running Tails is installed on USB drive "to_upgrade" 21.726
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.306
After features/support/hooks.rb:331 4.127
After features/support/hooks.rb:100 0.000
Tags: @product
1:36.330
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 2.781
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:23.862
Then all tps features from the old Tails version are active 1.459
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 4.220
And the expected persistent files created with the old Tails version are present in the filesystem 1.372
And all persistent directories from the old Tails version have safe access rights 2.316
After features/support/hooks.rb:331 1.154
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:48.833
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 25.077
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.060
And Tor is ready 15.775
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.724
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.267
Given I shutdown Tails and wait for the computer to power off 11.479
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.463
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.072
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.214
When the network is plugged 0.056
And Tor is ready 12.185
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.713
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.666
Given I shutdown Tails and wait for the computer to power off 8.988
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.129
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.058
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.051
And Tor is ready 13.285
Then the Upgrader considers the system as up-to-date 0.210
# 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 6.050
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.733
After features/support/hooks.rb:331 1.041
After features/support/hooks.rb:100 0.077
Tags: @product @automatic_upgrade
26.594
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 11.914
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 11.959
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.248
After features/support/hooks.rb:331 1.190
After features/support/hooks.rb:100 0.000