Project Number Date
test_Tails_ISO_stable 6117 04 Feb 2026, 08:03

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:40.072 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:43.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.426
When I start Tails from USB drive "old" with network unplugged 1:24.272
Then the boot device has safe access rights 2.954
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 1.472
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.887
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 57.187
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 25.395
And I take note of which tps features are available 0.847
Then a Tails persistence partition exists on USB drive "old" 0.627
And I shutdown Tails and wait for the computer to power off 8.469
After features/support/hooks.rb:331 0.439
After features/support/hooks.rb:100 0.008
Tags: @product
1:25.254
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.597
Then Tails is running from USB drive "old" 0.268
And all tps features are active 1.140
When I write some files expected to persist 1.341
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.332
And all persistent directories from the old Tails version have safe access rights 1.825
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 4.679
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.678
After features/support/hooks.rb:331 0.631
After features/support/hooks.rb:100 0.008
Tags: @product
2:28.332
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 9.242
And I log in to a new session 15.838
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.850
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.836
Then the running Tails is installed on USB drive "to_upgrade" 16.984
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:331 12.149
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.469
Then all tps features from the old Tails version are active 0.941
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 2.764
And the expected persistent files created with the old Tails version are present in the filesystem 1.145
And all persistent directories from the old Tails version have safe access rights 1.773
After features/support/hooks.rb:331 0.834
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:55.529
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 8.662
And no SquashFS delta is installed 0.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.028
And Tor is ready 13.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.488
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.165
Given I shutdown Tails and wait for the computer to power off 15.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.441
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.144
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
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.147
# 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.217
When the network is plugged 0.019
And Tor is ready 11.207
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.125
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.031
Given I shutdown Tails and wait for the computer to power off 7.890
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.614
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.077
And the file system changes introduced in version 6.3~testoverlayfs are present 0.335
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.018
And Tor is ready 9.899
Then the Upgrader considers the system as up-to-date 10.573
# 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.347
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.363
After features/support/hooks.rb:331 0.941
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
20.250
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.632
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.414
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.864
After features/support/hooks.rb:331 1.007
After features/support/hooks.rb:100 0.000