Project Number Date
test_Tails_ISO_stable 6413 01 Jun 2026, 11:23

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:0.613 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.650
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 12.958
When I start Tails from USB drive "old" with network unplugged 44.243
Then the boot device has safe access rights 2.706
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:335 1.223
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.455
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 52.690
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 23.465
And I take note of which tps features are available 0.359
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 8.099
After features/support/hooks.rb:335 0.476
After features/support/hooks.rb:104 0.006
Tags: @product
1:23.347
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.756
Then Tails is running from USB drive "old" 0.258
And all tps features are active 1.123
When I write some files expected to persist 1.124
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.129
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 1.952
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 7.936
# 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.572
After features/support/hooks.rb:335 0.474
After features/support/hooks.rb:104 0.007
Tags: @product
2:8.385
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.165
And I log in to a new session 11.527
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.752
And I plug USB drive "to_upgrade" 2.296
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.041
Then the running Tails is installed on USB drive "to_upgrade" 14.341
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:335 2.172
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.310
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 59.919
Then all tps features from the old Tails version are active 0.982
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 2.339
And the expected persistent files created with the old Tails version are present in the filesystem 1.048
And all persistent directories from the old Tails version have safe access rights 1.754
After features/support/hooks.rb:335 0.940
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:36.502
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.187
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
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.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.017
And Tor is ready 13.333
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.453
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.486
Given I shutdown Tails and wait for the computer to power off 10.746
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.041
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.297
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.251
When the network is plugged 0.015
And Tor is ready 10.039
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.861
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.121
Given I shutdown Tails and wait for the computer to power off 7.941
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.033
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.104
And the file system changes introduced in version 6.3~testoverlayfs are present 0.382
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.014
And Tor is ready 9.644
Then the Upgrader considers the system as up-to-date 10.538
# 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.767
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.361
After features/support/hooks.rb:335 0.879
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
18.962
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.338
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.012
And Tor is ready 9.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.638
After features/support/hooks.rb:335 0.824
After features/support/hooks.rb:104 0.000