Project Number Date
test_Tails_ISO_stable 6648 08 Sep 2026, 18:12

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:45.392 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:18.073
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.127
When I start Tails from USB drive "old" with network unplugged 59.931
Then the boot device has safe access rights 2.237
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.470
After features/support/hooks.rb:108 0.009
Tags: @product
1:23.506
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 48.895
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 23.447
And I take note of which tps features are available 6.325
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 3.939
After features/support/hooks.rb:339 0.330
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.866
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.791
Then Tails is running from USB drive "old" 0.219
And all tps features are active 7.899
When I write some files expected to persist 1.237
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.275
And all persistent directories from the old Tails version have safe access rights 1.922
And I take note of which tps features are available 6.883
And I shutdown Tails and wait for the computer to power off 4.332
# 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.011
After features/support/hooks.rb:339 0.488
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.741
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 without a persistent partition and stopped at Tails Greeter's login screen 9.320
And I log in to a new session 12.253
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.728
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.103
Then the running Tails is installed on USB drive "to_upgrade" 18.858
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 1.847
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.363
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.118
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.097
Then all tps features from the old Tails version are active 1.157
And Tails is running from USB drive "to_upgrade" 0.196
And the boot device has safe access rights 2.743
And the expected persistent files created with the old Tails version are present in the filesystem 1.125
And all persistent directories from the old Tails version have safe access rights 1.924
After features/support/hooks.rb:339 0.910
After features/support/hooks.rb:108 0.045
Tags: @product @automatic_upgrade
3:40.113
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.622
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.252
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.313
When the network is plugged 0.027
And Tor is ready 12.377
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.667
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.575
Given I shutdown Tails and wait for the computer to power off 5.497
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.047
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 7.687
And the file system changes introduced in version 6.2~testoverlayfs are present 0.163
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.112
# 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.187
When the network is plugged 0.023
And Tor is ready 10.496
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.913
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.812
Given I shutdown Tails and wait for the computer to power off 2.585
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.264
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 8.269
And the file system changes introduced in version 6.3~testoverlayfs are present 0.343
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.156
When the network is plugged 0.022
And Tor is ready 10.556
Then the Upgrader considers the system as up-to-date 0.104
# 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.070
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.326
After features/support/hooks.rb:339 0.762
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.728
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 8.299
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 10.110
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.965
After features/support/hooks.rb:339 1.005
After features/support/hooks.rb:108 0.000