Project Number Date
test_Tails_ISO_stable 6518 21 Jul 2026, 18:04

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:29.702 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:12.338
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 14.219
When I start Tails from USB drive "old" with network unplugged 53.363
Then the boot device has safe access rights 2.927
And Tails is running from USB drive "old" 0.257
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:339 1.375
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.941
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 57.197
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 26.035
And I take note of which tps features are available 4.699
Then a Tails persistence partition exists on USB drive "old" 0.629
And I shutdown Tails and wait for the computer to power off 8.058
After features/support/hooks.rb:339 0.465
After features/support/hooks.rb:108 0.006
Tags: @product
1:42.019
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.893
Then Tails is running from USB drive "old" 0.248
And all tps features are active 5.494
When I write some files expected to persist 1.320
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.311
And all persistent directories from the old Tails version have safe access rights 2.095
And I take note of which tps features are available 4.185
And I shutdown Tails and wait for the computer to power off 4.445
# 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.756
After features/support/hooks.rb:339 0.379
After features/support/hooks.rb:108 0.017
Tags: @product
2:15.088
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.138
And I log in to a new session 14.192
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.191
And I plug USB drive "to_upgrade" 2.294
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.027
Then the running Tails is installed on USB drive "to_upgrade" 16.967
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 0.896
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.043
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.405
Then all tps features from the old Tails version are active 1.194
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 2.712
And the expected persistent files created with the old Tails version are present in the filesystem 1.289
And all persistent directories from the old Tails version have safe access rights 2.055
After features/support/hooks.rb:339 0.684
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
4:5.065
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.581
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.365
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.048
And Tor is ready 12.954
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.990
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.632
Given I shutdown Tails and wait for the computer to power off 7.124
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.255
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 5.668
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.238
When the network is plugged 0.060
And Tor is ready 10.751
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.752
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.947
Given I shutdown Tails and wait for the computer to power off 4.093
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.989
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.781
And the file system changes introduced in version 6.3~testoverlayfs are present 0.404
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.014
And Tor is ready 10.485
Then the Upgrader considers the system as up-to-date 10.607
# 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.236
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.367
After features/support/hooks.rb:339 0.962
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
20.205
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.788
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 10.047
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.932
After features/support/hooks.rb:339 1.055
After features/support/hooks.rb:108 0.000