Project Number Date
test_Tails_ISO_stable 6475 29 Jun 2026, 11:38

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:15.204 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:11.372
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
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.860
When I start Tails from USB drive "old" with network unplugged 52.991
Then the boot device has safe access rights 2.777
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.174
And I unplug USB drive "old" 0.148
After features/support/hooks.rb:339 3.716
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.234
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 54.682
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 25.733
And I take note of which tps features are available 4.530
Then a Tails persistence partition exists on USB drive "old" 0.661
And I shutdown Tails and wait for the computer to power off 8.239
After features/support/hooks.rb:339 0.178
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.558
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.194
Then Tails is running from USB drive "old" 0.247
And all tps features are active 5.185
When I write some files expected to persist 1.186
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 1.788
And I take note of which tps features are available 3.963
And I shutdown Tails and wait for the computer to power off 8.299
# 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" 12.151
After features/support/hooks.rb:339 0.272
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.219
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 8.413
And I log in to a new session 12.386
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.889
And I plug USB drive "to_upgrade" 2.257
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.934
Then the running Tails is installed on USB drive "to_upgrade" 16.003
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:339 2.186
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.675
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.986
Then all tps features from the old Tails version are active 0.997
And Tails is running from USB drive "to_upgrade" 0.533
And the boot device has safe access rights 2.605
And the expected persistent files created with the old Tails version are present in the filesystem 1.285
And all persistent directories from the old Tails version have safe access rights 2.193
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
4:2.111
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 8.441
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
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.338
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.463
When the network is plugged 0.016
And Tor is ready 13.644
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.752
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.086
Given I shutdown Tails and wait for the computer to power off 11.218
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.063
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.252
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.226
When the network is plugged 0.019
And Tor is ready 11.364
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.622
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.002
Given I shutdown Tails and wait for the computer to power off 8.443
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.555
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 6.064
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.173
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.031
And Tor is ready 9.574
Then the Upgrader considers the system as up-to-date 10.493
# 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.237
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.408
After features/support/hooks.rb:339 0.849
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.032
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 7.265
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.655
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.676
After features/support/hooks.rb:339 0.739
After features/support/hooks.rb:108 0.000