Project Number Date
test_Tails_ISO_stable 6647 08 Sep 2026, 12:32

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:59.835 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:0.936
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.558
When I start Tails from USB drive "old" with network unplugged 41.909
Then the boot device has safe access rights 2.665
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 1.100
After features/support/hooks.rb:108 0.007
Tags: @product
1:31.651
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login 54.513
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 25.139
And I take note of which tps features are available 7.063
Then a Tails persistence partition exists on USB drive "old" 0.571
And I shutdown Tails and wait for the computer to power off 4.030
After features/support/hooks.rb:339 0.220
After features/support/hooks.rb:108 0.006
Tags: @product
1:48.884
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.123
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.475
Then Tails is running from USB drive "old" 0.193
And all tps features are active 12.668
When I write some files expected to persist 1.136
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.115
And all persistence configuration files have safe access rights 0.198
And all persistent directories from the old Tails version have safe access rights 1.652
And I take note of which tps features are available 6.075
And I shutdown Tails and wait for the computer to power off 3.985
# 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" 14.258
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.005
Tags: @product
2:19.673
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 without a persistent partition and stopped at Tails Greeter's login screen 10.331
And I log in to a new session 12.651
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.935
And I plug USB drive "to_upgrade" 2.302
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.038
Then the running Tails is installed on USB drive "to_upgrade" 19.177
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 3.548
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.641
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.838
Then all tps features from the old Tails version are active 1.160
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.501
And the expected persistent files created with the old Tails version are present in the filesystem 1.033
And all persistent directories from the old Tails version have safe access rights 1.788
After features/support/hooks.rb:339 0.604
After features/support/hooks.rb:108 0.034
Tags: @product @automatic_upgrade
3:43.699
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 9.460
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.181
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.027
And Tor is ready 11.664
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.172
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.315
Given I shutdown Tails and wait for the computer to power off 5.424
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.101
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.790
And the file system changes introduced in version 6.2~testoverlayfs are present 0.253
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.108
# 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.198
When the network is plugged 0.025
And Tor is ready 10.163
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.429
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.120
Given I shutdown Tails and wait for the computer to power off 4.222
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.514
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 9.149
And the file system changes introduced in version 6.3~testoverlayfs are present 0.345
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.030
And Tor is ready 10.600
Then the Upgrader considers the system as up-to-date 0.084
# 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.438
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.576
After features/support/hooks.rb:339 0.661
After features/support/hooks.rb:108 0.036
Tags: @product @automatic_upgrade
19.348
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.413
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
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.027
And Tor is ready 9.541
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.081
After features/support/hooks.rb:339 0.820
After features/support/hooks.rb:108 0.000