Project Number Date
test_Tails_ISO_stable-flatpak 46 14 Oct 2026, 19:41

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 10:57.305 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:3.260
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.056
When I start Tails from USB drive "old" with network unplugged 46.489
Then the boot device has safe access rights 1.971
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.076
And udev-watchdog is monitoring the correct device 0.152
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 3.745
After features/support/hooks.rb:108 0.038
Tags: @product
1:20.393
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 46.637
Then Tails is running from USB drive "old" 0.222
And I create a persistent partition 24.077
And I take note of which tps features are available 6.298
Then a Tails persistence partition exists on USB drive "old" 0.490
And I shutdown Tails and wait for the computer to power off 2.588
After features/support/hooks.rb:339 0.449
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.574
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.300
Then Tails is running from USB drive "old" 0.200
And all tps features are active 6.766
When I write some files expected to persist 1.218
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.110
And all persistence configuration files have safe access rights 0.204
And all persistent directories from the old Tails version have safe access rights 1.630
And I take note of which tps features are available 6.121
And I shutdown Tails and wait for the computer to power off 3.890
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.048
After features/support/hooks.rb:339 0.231
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.958
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.108
And I log in to a new session 9.982
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.616
And I plug USB drive "to_upgrade" 2.261
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:29.911
Then the running Tails is installed on USB drive "to_upgrade" 17.847
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.109
After features/support/hooks.rb:339 1.599
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.434
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.024
Then all tps features from the old Tails version are active 1.114
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 1.837
And the expected persistent files created with the old Tails version are present in the filesystem 1.213
And all persistent directories from the old Tails version have safe access rights 1.942
After features/support/hooks.rb:339 0.712
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:27.634
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.228
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.190
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.390
When the network is plugged 0.025
And Tor is ready 15.518
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.034
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.225
Given I shutdown Tails and wait for the computer to power off 5.261
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.604
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.997
And the file system changes introduced in version 6.2~testoverlayfs are present 0.196
And only the 6.2~testoverlayfs SquashFS delta is installed 0.033
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# 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.158
When the network is plugged 0.027
And Tor is ready 10.285
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.978
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.559
Given I shutdown Tails and wait for the computer to power off 4.014
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.120
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.370
And the file system changes introduced in version 6.3~testoverlayfs are present 0.301
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.136
When the network is plugged 0.025
And Tor is ready 10.250
Then the Upgrader considers the system as up-to-date 0.088
# 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 3.654
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.314
After features/support/hooks.rb:339 0.631
After features/support/hooks.rb:108 0.060
Tags: @product @automatic_upgrade
19.051
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.782
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.178
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.035
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 9.028
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.941
After features/support/hooks.rb:339 1.031
After features/support/hooks.rb:108 0.000