Project Number Date
test_Tails_ISO_stable 6432 07 Jun 2026, 07:21

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:56.194 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:1.649
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.066
When I start Tails from USB drive "old" with network unplugged 44.339
Then the boot device has safe access rights 2.504
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:335 3.573
After features/support/hooks.rb:104 0.015
Tags: @product
1:25.129
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 51.342
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 24.560
And I take note of which tps features are available 0.432
Then a Tails persistence partition exists on USB drive "old" 0.562
And I shutdown Tails and wait for the computer to power off 7.931
After features/support/hooks.rb:335 0.221
After features/support/hooks.rb:104 0.006
Tags: @product
1:23.020
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.635
Then Tails is running from USB drive "old" 0.194
And all tps features are active 1.069
When I write some files expected to persist 1.281
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.142
And all persistence configuration files have safe access rights 0.253
And all persistent directories from the old Tails version have safe access rights 1.731
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 7.837
# 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.676
After features/support/hooks.rb:335 0.274
After features/support/hooks.rb:104 0.006
Tags: @product
2:7.682
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.930
And I log in to a new session 11.542
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.739
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.070
Then the running Tails is installed on USB drive "to_upgrade" 13.902
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:335 1.965
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.473
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.716
Then all tps features from the old Tails version are active 1.007
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.612
And the expected persistent files created with the old Tails version are present in the filesystem 1.056
And all persistent directories from the old Tails version have safe access rights 1.798
After features/support/hooks.rb:335 0.826
After features/support/hooks.rb:104 0.005
Tags: @product @automatic_upgrade
3:32.266
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.039
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.321
When the network is plugged 0.016
And Tor is ready 12.068
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.872
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.219
Given I shutdown Tails and wait for the computer to power off 9.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.718
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.174
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
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.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.197
When the network is plugged 0.015
And Tor is ready 9.759
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.133
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.210
Given I shutdown Tails and wait for the computer to power off 7.820
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.906
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.070
And the file system changes introduced in version 6.3~testoverlayfs are present 0.349
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.019
And Tor is ready 10.831
Then the Upgrader considers the system as up-to-date 10.490
# 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.907
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.472
After features/support/hooks.rb:335 0.648
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
19.972
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.326
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.189
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.682
After features/support/hooks.rb:335 0.777
After features/support/hooks.rb:104 0.000