Project Number Date
test_Tails_ISO_stable 6311 20 Apr 2026, 13:57

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 13:49.087 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.711
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.388
When I start Tails from USB drive "old" with network unplugged 59.197
Then the boot device has safe access rights 3.132
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.242
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:331 3.873
After features/support/hooks.rb:100 0.017
Tags: @product
1:31.923
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 56.820
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 26.294
And I take note of which tps features are available 0.802
Then a Tails persistence partition exists on USB drive "old" 0.573
And I shutdown Tails and wait for the computer to power off 7.097
After features/support/hooks.rb:331 0.475
After features/support/hooks.rb:100 0.006
Tags: @product
1:35.416
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.502
Then Tails is running from USB drive "old" 0.238
And all tps features are active 1.392
When I write some files expected to persist 1.472
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.492
And all persistent directories from the old Tails version have safe access rights 2.527
And I take note of which tps features are available 0.193
And I shutdown Tails and wait for the computer to power off 7.185
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.075
After features/support/hooks.rb:331 0.414
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.845
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.493
And I log in to a new session 14.359
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.043
And I plug USB drive "to_upgrade" 2.262
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.751
Then the running Tails is installed on USB drive "to_upgrade" 17.636
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.159
After features/support/hooks.rb:331 2.281
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.929
Then all tps features from the old Tails version are active 1.068
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.834
And the expected persistent files created with the old Tails version are present in the filesystem 1.453
And all persistent directories from the old Tails version have safe access rights 2.303
After features/support/hooks.rb:331 0.834
After features/support/hooks.rb:100 0.010
5:19.224
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.468
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.028
And Tor is ready 43.811
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.470
Given I shutdown Tails and wait for the computer to power off 15.267
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.507
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 1.270
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.483
When the network is plugged 0.026
And Tor is ready 22.064
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.399
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.859
Given I shutdown Tails and wait for the computer to power off 18.682
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.478
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.180
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.027
And Tor is ready 21.767
Then the Upgrader considers the system as up-to-date 0.112
# 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.872
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.462
After features/support/hooks.rb:331 0.938
After features/support/hooks.rb:100 0.014
29.053
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.907
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 19.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.453
After features/support/hooks.rb:331 0.813
After features/support/hooks.rb:100 0.000