Project Number Date
test_Tails_ISO_stable 6706 29 Sep 2026, 15:54

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 11:1.474 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:9.582
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.456
When I start Tails from USB drive "old" with network unplugged 52.193
Then the boot device has safe access rights 2.153
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.163
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:339 3.477
After features/support/hooks.rb:108 0.006
Tags: @product
1:21.065
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 47.966
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 23.319
And I take note of which tps features are available 6.390
Then a Tails persistence partition exists on USB drive "old" 0.470
And I shutdown Tails and wait for the computer to power off 2.550
After features/support/hooks.rb:339 0.235
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.042
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.655
Then Tails is running from USB drive "old" 0.177
And all tps features are active 7.227
When I write some files expected to persist 1.356
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 1.889
And I take note of which tps features are available 6.102
And I shutdown Tails and wait for the computer to power off 2.528
# 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.571
After features/support/hooks.rb:339 0.293
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.767
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.314
And I log in to a new session 11.965
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.644
And I plug USB drive "to_upgrade" 2.686
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.844
Then the running Tails is installed on USB drive "to_upgrade" 18.072
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.570
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.788
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.123
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.085
Then all tps features from the old Tails version are active 1.136
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 1.924
And the expected persistent files created with the old Tails version are present in the filesystem 0.836
And all persistent directories from the old Tails version have safe access rights 1.453
After features/support/hooks.rb:339 0.864
After features/support/hooks.rb:108 0.021
3:22.373
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.082
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.047
And Tor is ready 13.391
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.305
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.690
Given I shutdown Tails and wait for the computer to power off 5.219
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.204
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.683
And the file system changes introduced in version 6.2~testoverlayfs are present 0.166
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.090
# 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.155
When the network is plugged 0.022
And Tor is ready 10.059
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.289
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.717
Given I shutdown Tails and wait for the computer to power off 2.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.451
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.035
And the file system changes introduced in version 6.3~testoverlayfs are present 0.219
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.071
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.167
When the network is plugged 0.035
And Tor is ready 11.238
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 4.053
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.302
After features/support/hooks.rb:339 1.090
After features/support/hooks.rb:108 0.028
17.853
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.894
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.176
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.031
And Tor is ready 8.206
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.455
After features/support/hooks.rb:339 0.794
After features/support/hooks.rb:108 0.000