Project Number Date
test_Tails_ISO_stable 6149 16 Feb 2026, 11: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:9.157 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:38.114
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.929
When I start Tails from USB drive "old" with network unplugged 1:19.876
Then the boot device has safe access rights 2.561
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 3.756
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.578
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 57.525
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 24.252
And I take note of which tps features are available 0.794
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 8.156
After features/support/hooks.rb:331 0.288
After features/support/hooks.rb:100 0.007
Tags: @product
1:22.020
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.635
Then Tails is running from USB drive "old" 0.230
And all tps features are active 1.020
When I write some files expected to persist 1.177
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.814
And I take note of which tps features are available 0.155
And I shutdown Tails and wait for the computer to power off 4.307
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.160
After features/support/hooks.rb:331 0.350
After features/support/hooks.rb:100 0.006
Tags: @product
2:16.515
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.143
And I log in to a new session 14.392
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.761
And I plug USB drive "to_upgrade" 2.288
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.726
Then the running Tails is installed on USB drive "to_upgrade" 15.912
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.162
After features/support/hooks.rb:331 3.691
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.636
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.948
Then all tps features from the old Tails version are active 0.890
And Tails is running from USB drive "to_upgrade" 0.277
And the boot device has safe access rights 2.392
And the expected persistent files created with the old Tails version are present in the filesystem 1.066
And all persistent directories from the old Tails version have safe access rights 2.014
After features/support/hooks.rb:331 0.753
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:52.067
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.241
And no SquashFS delta is installed 0.162
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.020
And Tor is ready 14.470
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.675
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.480
Given I shutdown Tails and wait for the computer to power off 11.126
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.898
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.073
And the file system changes introduced in version 6.2~testoverlayfs are present 0.197
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.219
When the network is plugged 0.016
And Tor is ready 10.018
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.684
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.186
Given I shutdown Tails and wait for the computer to power off 8.178
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.092
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.275
And the file system changes introduced in version 6.3~testoverlayfs are present 0.377
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.016
And Tor is ready 11.095
Then the Upgrader considers the system as up-to-date 10.514
# 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.109
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:331 0.944
After features/support/hooks.rb:100 0.049
Tags: @product @automatic_upgrade
21.224
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 7.856
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.002
When the network is plugged 0.018
And Tor is ready 11.170
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.850
After features/support/hooks.rb:331 1.007
After features/support/hooks.rb:100 0.000