Project Number Date
test_Tails_ISO_stable 6164 24 Feb 2026, 11:55

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 15:2.661 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:30.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 27.191
When I start Tails from USB drive "old" with network unplugged 58.349
Then the boot device has safe access rights 3.059
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.251
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:331 3.529
After features/support/hooks.rb:100 0.009
Tags: @product
1:43.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:4.415
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 29.159
And I take note of which tps features are available 1.141
Then a Tails persistence partition exists on USB drive "old" 0.653
And I shutdown Tails and wait for the computer to power off 7.890
After features/support/hooks.rb:331 0.242
After features/support/hooks.rb:100 0.010
Tags: @product
1:49.746
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:15.707
Then Tails is running from USB drive "old" 0.328
And all tps features are active 2.143
When I write some files expected to persist 1.629
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.538
And all persistent directories from the old Tails version have safe access rights 2.221
And I take note of which tps features are available 0.500
And I shutdown Tails and wait for the computer to power off 7.843
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.490
After features/support/hooks.rb:331 0.256
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.888
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 9.599
And I log in to a new session 10.767
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.631
And I plug USB drive "to_upgrade" 2.493
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.202
Then the running Tails is installed on USB drive "to_upgrade" 18.800
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:331 1.613
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.955
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.447
Then all tps features from the old Tails version are active 1.419
And Tails is running from USB drive "to_upgrade" 0.302
And the boot device has safe access rights 2.944
And the expected persistent files created with the old Tails version are present in the filesystem 1.346
And all persistent directories from the old Tails version have safe access rights 2.311
After features/support/hooks.rb:331 1.035
After features/support/hooks.rb:100 0.008
5:22.081
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 10.147
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.068
And Tor is ready 19.490
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.576
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.495
Given I shutdown Tails and wait for the computer to power off 17.995
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:29.491
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.675
And the file system changes introduced in version 6.2~testoverlayfs are present 0.249
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.235
When the network is plugged 0.061
And Tor is ready 23.187
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.631
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.936
Given I shutdown Tails and wait for the computer to power off 18.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:30.603
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.310
And the file system changes introduced in version 6.3~testoverlayfs are present 0.402
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.053
And Tor is ready 22.735
Then the Upgrader considers the system as up-to-date 0.132
# 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.933
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.521
After features/support/hooks.rb:331 1.282
After features/support/hooks.rb:100 0.019
50.492
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 9.698
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 39.692
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.632
After features/support/hooks.rb:331 0.908
After features/support/hooks.rb:100 0.000