Project Number Date
test_Tails_ISO_stable 6484 01 Jul 2026, 07: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:33.073 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:4.076
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.228
When I start Tails from USB drive "old" with network unplugged 46.591
Then the boot device has safe access rights 2.557
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.350
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.657
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 51.297
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 23.550
And I take note of which tps features are available 3.717
Then a Tails persistence partition exists on USB drive "old" 0.494
And I shutdown Tails and wait for the computer to power off 8.307
After features/support/hooks.rb:339 0.230
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.867
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.820
Then Tails is running from USB drive "old" 0.225
And all tps features are active 4.641
When I write some files expected to persist 1.304
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.280
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 3.556
And I shutdown Tails and wait for the computer to power off 8.216
# 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.643
After features/support/hooks.rb:339 0.454
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.436
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 7.781
And I log in to a new session 11.275
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.834
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.368
Then the running Tails is installed on USB drive "to_upgrade" 14.697
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:339 2.306
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.380
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.876
Then all tps features from the old Tails version are active 0.871
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.322
And the expected persistent files created with the old Tails version are present in the filesystem 1.158
And all persistent directories from the old Tails version have safe access rights 1.848
After features/support/hooks.rb:339 0.828
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:49.417
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.147
And no SquashFS delta is installed 0.053
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.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.019
And Tor is ready 12.974
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.576
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.361
Given I shutdown Tails and wait for the computer to power off 9.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.146
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.855
And the file system changes introduced in version 6.2~testoverlayfs are present 0.227
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.202
When the network is plugged 0.016
And Tor is ready 10.870
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.658
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.212
Given I shutdown Tails and wait for the computer to power off 7.921
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.606
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.756
And the file system changes introduced in version 6.3~testoverlayfs are present 0.328
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.019
And Tor is ready 10.577
Then the Upgrader considers the system as up-to-date 10.557
# 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.131
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.332
After features/support/hooks.rb:339 1.014
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
19.238
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.311
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
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.076
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 8.431
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.145
After features/support/hooks.rb:339 0.971
After features/support/hooks.rb:108 0.000