Project Number Date
test_Tails_ISO_stable 6489 06 Jul 2026, 07:38

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:10.580 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:1.516
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.799
When I start Tails from USB drive "old" with network unplugged 43.184
Then the boot device has safe access rights 2.774
And Tails is running from USB drive "old" 0.221
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.206
And I unplug USB drive "old" 0.163
After features/support/hooks.rb:339 1.254
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.117
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 54.761
Then Tails is running from USB drive "old" 0.193
And I create a persistent partition 25.474
And I take note of which tps features are available 4.948
Then a Tails persistence partition exists on USB drive "old" 0.648
And I shutdown Tails and wait for the computer to power off 7.041
After features/support/hooks.rb:339 0.261
After features/support/hooks.rb:108 0.007
Tags: @product
1:41.879
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.538
Then Tails is running from USB drive "old" 0.235
And all tps features are active 5.428
When I write some files expected to persist 1.605
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 2.175
And I take note of which tps features are available 3.953
And I shutdown Tails and wait for the computer to power off 8.020
# 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.374
After features/support/hooks.rb:339 0.491
After features/support/hooks.rb:108 0.007
Tags: @product
2:11.984
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.307
And I log in to a new session 13.149
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.814
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.939
Then the running Tails is installed on USB drive "to_upgrade" 15.223
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 2.154
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.839
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.920
Then all tps features from the old Tails version are active 1.097
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 3.012
And the expected persistent files created with the old Tails version are present in the filesystem 1.249
And all persistent directories from the old Tails version have safe access rights 2.247
After features/support/hooks.rb:339 0.944
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
4:2.887
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.309
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.014
And Tor is ready 12.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.673
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.294
Given I shutdown Tails and wait for the computer to power off 9.666
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.771
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.988
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
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.141
# 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.264
When the network is plugged 0.013
And Tor is ready 10.117
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.125
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.957
Given I shutdown Tails and wait for the computer to power off 8.197
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.268
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 5.468
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.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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.016
And Tor is ready 10.176
Then the Upgrader considers the system as up-to-date 10.543
# 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.750
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.388
After features/support/hooks.rb:339 1.121
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
21.354
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 7.332
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 10.354
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.276
After features/support/hooks.rb:339 0.857
After features/support/hooks.rb:108 0.000