Project Number Date
test_Tails_ISO_stable 6449 16 Jun 2026, 14:09

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 12:46.072 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:15.038
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.162
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 13.988
When I start Tails from USB drive "old" with network unplugged 55.507
Then the boot device has safe access rights 3.552
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 3.614
After features/support/hooks.rb:108 0.021
Tags: @product
1:34.153
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.144
And I start Tails from USB drive "old" with network unplugged and I login 55.339
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 26.413
And I take note of which tps features are available 4.218
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 7.274
After features/support/hooks.rb:339 0.246
After features/support/hooks.rb:108 0.021
Tags: @product
1:44.309
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.572
Then Tails is running from USB drive "old" 0.243
And all tps features are active 5.132
When I write some files expected to persist 1.352
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.284
And all persistent directories from the old Tails version have safe access rights 2.340
And I take note of which tps features are available 4.727
And I shutdown Tails and wait for the computer to power off 7.129
# 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" 13.159
After features/support/hooks.rb:339 0.589
After features/support/hooks.rb:108 0.022
Tags: @product
2:15.748
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.926
And I log in to a new session 14.971
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.835
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.718
Then the running Tails is installed on USB drive "to_upgrade" 15.736
And I unplug USB drive "to_upgrade" 0.165
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:339 0.923
After features/support/hooks.rb:108 0.000
Tags: @product
1:20.523
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.024
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.147
Then all tps features from the old Tails version are active 1.215
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 3.123
And the expected persistent files created with the old Tails version are present in the filesystem 1.224
And all persistent directories from the old Tails version have safe access rights 2.385
After features/support/hooks.rb:339 0.842
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
4:12.868
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.096
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.014
And Tor is ready 13.892
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.165
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.624
Given I shutdown Tails and wait for the computer to power off 10.500
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.934
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.072
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.240
When the network is plugged 0.017
And Tor is ready 10.085
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.824
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.747
Given I shutdown Tails and wait for the computer to power off 4.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.992
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.441
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.035
And Tor is ready 11.361
Then the Upgrader considers the system as up-to-date 10.512
# 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.384
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:339 0.623
After features/support/hooks.rb:108 0.040
Tags: @product @automatic_upgrade
23.429
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.811
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 11.745
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.485
After features/support/hooks.rb:339 0.786
After features/support/hooks.rb:108 0.000