Project Number Date
test_Tails_ISO_stable 6172 25 Feb 2026, 17:36

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:37.020 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:11.476
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.393
When I start Tails from USB drive "old" with network unplugged 53.840
Then the boot device has safe access rights 2.412
And Tails is running from USB drive "old" 0.276
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:331 1.358
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.244
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 55.555
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 24.167
And I take note of which tps features are available 0.662
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 4.064
After features/support/hooks.rb:331 0.606
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.703
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.553
Then Tails is running from USB drive "old" 0.227
And all tps features are active 1.080
When I write some files expected to persist 1.110
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.277
And all persistent directories from the old Tails version have safe access rights 1.786
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 7.856
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.411
After features/support/hooks.rb:331 0.124
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.611
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 7.727
And I log in to a new session 13.109
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.682
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.750
Then the running Tails is installed on USB drive "to_upgrade" 17.861
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 3.703
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.655
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.038
Then all tps features from the old Tails version are active 0.917
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.452
And the expected persistent files created with the old Tails version are present in the filesystem 1.032
And all persistent directories from the old Tails version have safe access rights 1.927
After features/support/hooks.rb:331 0.545
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:37.133
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 with a persistent partition enabled and logged in 8.277
And no SquashFS delta is installed 0.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.373
When the network is plugged 0.020
And Tor is ready 24.699
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.355
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.938
Given I shutdown Tails and wait for the computer to power off 20.707
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.347
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.058
And the file system changes introduced in version 6.2~testoverlayfs are present 0.246
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.199
When the network is plugged 0.019
And Tor is ready 20.395
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.409
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.824
Given I shutdown Tails and wait for the computer to power off 18.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.695
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.038
And the file system changes introduced in version 6.3~testoverlayfs are present 0.417
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.014
And Tor is ready 20.904
Then the Upgrader considers the system as up-to-date 0.110
# 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.158
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.321
After features/support/hooks.rb:331 0.764
After features/support/hooks.rb:100 0.058
Tags: @product @automatic_upgrade
30.196
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.497
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 22.019
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.346
After features/support/hooks.rb:331 0.815
After features/support/hooks.rb:100 0.000