Project Number Date
test_Tails_ISO_devel 4571 26 Aug 2026, 18:27

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:58.990 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
57.002
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.319
When I start Tails from USB drive "old" with network unplugged 39.886
Then the boot device has safe access rights 2.019
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 1.719
After features/support/hooks.rb:108 0.006
Tags: @product
1:20.578
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 47.806
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 23.116
And I take note of which tps features are available 6.230
Then a Tails persistence partition exists on USB drive "old" 0.496
And I shutdown Tails and wait for the computer to power off 2.615
After features/support/hooks.rb:339 0.279
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.420
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.049
Then Tails is running from USB drive "old" 0.306
And all tps features are active 7.407
When I write some files expected to persist 1.193
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.146
And all persistence configuration files have safe access rights 0.346
And all persistent directories from the old Tails version have safe access rights 1.738
And I take note of which tps features are available 5.712
And I shutdown Tails and wait for the computer to power off 2.572
# 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.857
After features/support/hooks.rb:339 0.384
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.269
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.989
And I log in to a new session 12.218
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.587
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.870
Then the running Tails is installed on USB drive "to_upgrade" 18.079
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:339 1.824
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.056
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.126
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.450
Then all tps features from the old Tails version are active 1.095
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.065
And the expected persistent files created with the old Tails version are present in the filesystem 0.780
And all persistent directories from the old Tails version have safe access rights 1.309
After features/support/hooks.rb:339 0.586
After features/support/hooks.rb:108 0.007
3:30.793
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.023
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.197
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.037
And Tor is ready 11.973
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.078
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.617
Given I shutdown Tails and wait for the computer to power off 5.643
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.173
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.466
And the file system changes introduced in version 6.2~testoverlayfs are present 0.244
And only the 6.2~testoverlayfs SquashFS delta is installed 0.131
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.193
When the network is plugged 0.031
And Tor is ready 10.174
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.860
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.498
Given I shutdown Tails and wait for the computer to power off 2.554
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.816
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 7.932
And the file system changes introduced in version 6.3~testoverlayfs are present 0.330
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.105
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.027
And Tor is ready 10.392
Then the Upgrader considers the system as up-to-date 0.142
# 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.770
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.292
After features/support/hooks.rb:339 0.962
After features/support/hooks.rb:108 0.009
18.869
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.937
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.168
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.025
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.695
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.967
After features/support/hooks.rb:339 0.861
After features/support/hooks.rb:108 0.000