Project Number Date
test_Tails_ISO_stable 6141 11 Feb 2026, 19:31

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:19.386 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:15.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 15.029
When I start Tails from USB drive "old" with network unplugged 55.014
Then the boot device has safe access rights 3.411
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.161
After features/support/hooks.rb:331 3.941
After features/support/hooks.rb:100 0.007
Tags: @product
1:36.382
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 59.224
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 28.155
And I take note of which tps features are available 0.839
Then a Tails persistence partition exists on USB drive "old" 0.730
And I shutdown Tails and wait for the computer to power off 7.111
After features/support/hooks.rb:331 0.539
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.335
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 with persistence enabled 1:6.560
Then Tails is running from USB drive "old" 0.265
And all tps features are active 1.211
When I write some files expected to persist 1.781
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.309
And all persistent directories from the old Tails version have safe access rights 2.534
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 4.267
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.956
After features/support/hooks.rb:331 0.594
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.471
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.881
And I log in to a new session 12.455
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.015
And I plug USB drive "to_upgrade" 2.321
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.622
Then the running Tails is installed on USB drive "to_upgrade" 16.857
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.157
After features/support/hooks.rb:331 2.441
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.542
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.126
Then all tps features from the old Tails version are active 1.136
And Tails is running from USB drive "to_upgrade" 0.243
And the boot device has safe access rights 2.706
And the expected persistent files created with the old Tails version are present in the filesystem 1.207
And all persistent directories from the old Tails version have safe access rights 2.063
After features/support/hooks.rb:331 0.897
After features/support/hooks.rb:100 0.046
Tags: @product @automatic_upgrade
4:3.089
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 9.142
And no SquashFS delta is installed 0.079
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.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.536
When the network is plugged 0.015
And Tor is ready 14.099
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.970
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.390
Given I shutdown Tails and wait for the computer to power off 11.056
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.558
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.228
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.238
When the network is plugged 0.016
And Tor is ready 11.661
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.904
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.384
Given I shutdown Tails and wait for the computer to power off 8.864
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.177
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.160
And the file system changes introduced in version 6.3~testoverlayfs are present 0.378
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.018
And Tor is ready 12.292
Then the Upgrader considers the system as up-to-date 10.673
# 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 5.241
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.538
After features/support/hooks.rb:331 1.005
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
21.190
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 with a persistent partition enabled and logged in 8.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.161
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.538
After features/support/hooks.rb:331 1.139
After features/support/hooks.rb:100 0.000