Project Number Date
test_Tails_ISO_stable 6588 18 Aug 2026, 11:37

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:21.234 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
58.815
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.364
When I start Tails from USB drive "old" with network unplugged 41.756
Then the boot device has safe access rights 2.028
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.132
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 3.730
After features/support/hooks.rb:108 0.006
Tags: @product
1:20.832
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 46.198
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 23.099
And I take note of which tps features are available 6.526
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 4.069
After features/support/hooks.rb:339 0.476
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.964
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.008
Then Tails is running from USB drive "old" 0.183
And all tps features are active 7.167
When I write some files expected to persist 1.228
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.121
And all persistence configuration files have safe access rights 0.236
And all persistent directories from the old Tails version have safe access rights 1.556
And I take note of which tps features are available 6.154
And I shutdown Tails and wait for the computer to power off 2.573
# 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" 11.653
After features/support/hooks.rb:339 0.331
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.166
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 8.278
And I log in to a new session 11.097
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.752
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.330
Then the running Tails is installed on USB drive "to_upgrade" 17.226
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.812
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.130
Then all tps features from the old Tails version are active 1.514
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.313
And the expected persistent files created with the old Tails version are present in the filesystem 0.951
And all persistent directories from the old Tails version have safe access rights 1.605
After features/support/hooks.rb:339 0.810
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
3:51.371
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 21.134
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.177
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.024
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.324
When the network is plugged 0.031
And Tor is ready 12.184
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.577
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.698
Given I shutdown Tails and wait for the computer to power off 5.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.153
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.165
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.027
And Tor is ready 10.364
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.012
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.516
Given I shutdown Tails and wait for the computer to power off 2.640
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.375
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.423
And the file system changes introduced in version 6.3~testoverlayfs are present 0.252
And only the 6.3~testoverlayfs SquashFS delta is installed 0.030
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.208
When the network is plugged 0.032
And Tor is ready 10.316
Then the Upgrader considers the system as up-to-date 10.385
# 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.536
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.414
After features/support/hooks.rb:339 0.932
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.271
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.856
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.023
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 9.510
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.494
After features/support/hooks.rb:339 0.914
After features/support/hooks.rb:108 0.000