Project Number Date
test_Tails_ISO_stable 6144 12 Feb 2026, 12:13

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:3.159 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:16.183
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.054
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.312
When I start Tails from USB drive "old" with network unplugged 57.223
Then the boot device has safe access rights 2.848
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.148
After features/support/hooks.rb:331 1.569
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.814
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 58.079
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 24.225
And I take note of which tps features are available 0.795
Then a Tails persistence partition exists on USB drive "old" 0.636
And I shutdown Tails and wait for the computer to power off 2.764
After features/support/hooks.rb:331 0.513
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.826
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.056
Then Tails is running from USB drive "old" 0.241
And all tps features are active 1.080
When I write some files expected to persist 1.378
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 2.276
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 8.225
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.847
After features/support/hooks.rb:331 0.548
After features/support/hooks.rb:100 0.011
Tags: @product
2:17.969
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 without a persistent partition and stopped at Tails Greeter's login screen 8.230
And I log in to a new session 12.733
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.951
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.296
Then the running Tails is installed on USB drive "to_upgrade" 16.980
And I unplug USB drive "to_upgrade" 0.360
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:331 8.154
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.039
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.571
Then all tps features from the old Tails version are active 1.009
And Tails is running from USB drive "to_upgrade" 0.226
And the boot device has safe access rights 2.575
And the expected persistent files created with the old Tails version are present in the filesystem 1.483
And all persistent directories from the old Tails version have safe access rights 2.110
After features/support/hooks.rb:331 0.859
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:0.090
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.545
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.014
And Tor is ready 12.885
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.524
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.703
Given I shutdown Tails and wait for the computer to power off 12.845
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.588
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 2.378
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# 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.242
When the network is plugged 0.014
And Tor is ready 12.585
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.873
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.006
Given I shutdown Tails and wait for the computer to power off 8.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.994
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.586
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.041
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.223
When the network is plugged 0.014
And Tor is ready 11.947
Then the Upgrader considers the system as up-to-date 10.569
# 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.972
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.506
After features/support/hooks.rb:331 0.928
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
20.236
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.699
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 8.852
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.353
After features/support/hooks.rb:331 1.057
After features/support/hooks.rb:100 0.000