Project Number Date
test_Tails_ISO_stable 6155 18 Feb 2026, 19:51

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 13:15.469 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:31.713
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.050
When I start Tails from USB drive "old" with network unplugged 1:13.215
Then the boot device has safe access rights 2.665
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 1.466
After features/support/hooks.rb:100 0.006
Tags: @product
1:35.741
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 1:0.870
Then Tails is running from USB drive "old" 0.269
And I create a persistent partition 25.099
And I take note of which tps features are available 0.690
Then a Tails persistence partition exists on USB drive "old" 0.565
And I shutdown Tails and wait for the computer to power off 8.187
After features/support/hooks.rb:331 0.138
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.309
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.506
Then Tails is running from USB drive "old" 0.285
And all tps features are active 1.133
When I write some files expected to persist 1.669
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.354
And all persistent directories from the old Tails version have safe access rights 2.029
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 8.297
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.582
After features/support/hooks.rb:331 0.566
After features/support/hooks.rb:100 0.007
Tags: @product
2:15.026
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 without a persistent partition and stopped at Tails Greeter's login screen 8.013
And I log in to a new session 12.735
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.780
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.948
Then the running Tails is installed on USB drive "to_upgrade" 16.817
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.338
After features/support/hooks.rb:331 3.590
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.562
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.613
Then all tps features from the old Tails version are active 0.959
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.713
And the expected persistent files created with the old Tails version are present in the filesystem 1.054
And all persistent directories from the old Tails version have safe access rights 1.896
After features/support/hooks.rb:331 0.670
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
4:43.802
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 8.211
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.384
When the network is plugged 0.030
And Tor is ready 28.466
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.429
Given I shutdown Tails and wait for the computer to power off 15.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.881
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.141
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.044
# 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.213
When the network is plugged 0.014
And Tor is ready 21.689
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.354
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.960
Given I shutdown Tails and wait for the computer to power off 17.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.836
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.035
And the file system changes introduced in version 6.3~testoverlayfs are present 0.363
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.016
And Tor is ready 21.309
Then the Upgrader considers the system as up-to-date 0.123
# 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.404
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.389
After features/support/hooks.rb:331 0.721
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
29.313
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.647
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 20.842
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.461
After features/support/hooks.rb:331 1.001
After features/support/hooks.rb:100 0.000