Project Number Date
test_Tails_ISO_stable 6223 23 Mar 2026, 14:50

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 12:33.178 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:19.646
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.884
When I start Tails from USB drive "old" with network unplugged 1:1.051
Then the boot device has safe access rights 2.875
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:331 1.566
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.431
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 56.335
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 25.014
And I take note of which tps features are available 0.974
Then a Tails persistence partition exists on USB drive "old" 0.580
And I shutdown Tails and wait for the computer to power off 4.232
After features/support/hooks.rb:331 0.466
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.482
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.828
Then Tails is running from USB drive "old" 0.302
And all tps features are active 1.216
When I write some files expected to persist 1.330
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 2.103
And I take note of which tps features are available 0.247
And I shutdown Tails and wait for the computer to power off 4.282
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.452
After features/support/hooks.rb:331 0.349
After features/support/hooks.rb:100 0.006
Tags: @product
2:13.708
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.799
And I log in to a new session 13.038
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.846
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.133
Then the running Tails is installed on USB drive "to_upgrade" 16.355
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 2.389
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.036
Then all tps features from the old Tails version are active 1.019
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.714
And the expected persistent files created with the old Tails version are present in the filesystem 1.243
And all persistent directories from the old Tails version have safe access rights 2.258
After features/support/hooks.rb:331 0.715
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
4:28.797
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.317
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.016
And Tor is ready 22.547
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.560
Given I shutdown Tails and wait for the computer to power off 19.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.339
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 1.203
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.221
When the network is plugged 0.021
And Tor is ready 20.246
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.402
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.431
Given I shutdown Tails and wait for the computer to power off 13.484
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.957
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.314
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.029
And Tor is ready 20.721
Then the Upgrader considers the system as up-to-date 0.118
# 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 4.496
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.409
After features/support/hooks.rb:331 0.660
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
25.522
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.690
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 17.100
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.378
After features/support/hooks.rb:331 0.771
After features/support/hooks.rb:100 0.000