Project Number Date
test_Tails_ISO_stable 6747 13 Oct 2026, 22:07

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:42.905 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.715
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.598
When I start Tails from USB drive "old" with network unplugged 57.736
Then the boot device has safe access rights 2.400
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.826
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.683
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login 48.718
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 24.580
And I take note of which tps features are available 7.250
Then a Tails persistence partition exists on USB drive "old" 0.597
And I shutdown Tails and wait for the computer to power off 4.185
After features/support/hooks.rb:339 0.160
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.893
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.248
Then Tails is running from USB drive "old" 0.191
And all tps features are active 7.353
When I write some files expected to persist 1.299
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 1.876
And I take note of which tps features are available 6.893
And I shutdown Tails and wait for the computer to power off 4.069
# 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.299
After features/support/hooks.rb:339 0.470
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.612
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.550
And I log in to a new session 13.467
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.266
Then the running Tails is installed on USB drive "to_upgrade" 19.085
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.978
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.327
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.031
Then all tps features from the old Tails version are active 1.119
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.133
And the expected persistent files created with the old Tails version are present in the filesystem 1.074
And all persistent directories from the old Tails version have safe access rights 1.652
After features/support/hooks.rb:339 0.888
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:39.484
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.517
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
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.233
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.023
And Tor is ready 12.537
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.065
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.773
Given I shutdown Tails and wait for the computer to power off 5.453
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.547
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.426
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.182
When the network is plugged 0.022
And Tor is ready 10.258
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.914
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.161
Given I shutdown Tails and wait for the computer to power off 5.163
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.893
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.086
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.168
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.029
And Tor is ready 10.493
Then the Upgrader considers the system as up-to-date 0.086
# 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.246
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.323
After features/support/hooks.rb:339 0.965
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.189
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.916
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.394
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.507
After features/support/hooks.rb:339 1.065
After features/support/hooks.rb:108 0.000