Project Number Date
test_Tails_ISO_devel 4408 21 May 2026, 11:24

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:46.836 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:14.104
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.241
When I start Tails from USB drive "old" with network unplugged 55.126
Then the boot device has safe access rights 2.921
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.254
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:335 1.236
After features/support/hooks.rb:104 0.007
Tags: @product
1:25.074
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 55.142
Then Tails is running from USB drive "old" 0.216
And I create a persistent partition 24.516
And I take note of which tps features are available 0.379
Then a Tails persistence partition exists on USB drive "old" 0.542
And I shutdown Tails and wait for the computer to power off 4.222
After features/support/hooks.rb:335 0.253
After features/support/hooks.rb:104 0.006
Tags: @product
1:31.352
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.287
Then Tails is running from USB drive "old" 0.231
And all tps features are active 1.163
When I write some files expected to persist 1.445
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 2.171
And I take note of which tps features are available 0.167
And I shutdown Tails and wait for the computer to power off 8.071
# 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" 13.106
After features/support/hooks.rb:335 0.482
After features/support/hooks.rb:104 0.007
Tags: @product
2:15.241
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.435
And I log in to a new session 14.880
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.948
Then the running Tails is installed on USB drive "to_upgrade" 16.711
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:335 2.262
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.989
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.097
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.485
Then all tps features from the old Tails version are active 1.080
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.648
And the expected persistent files created with the old Tails version are present in the filesystem 1.377
And all persistent directories from the old Tails version have safe access rights 2.083
After features/support/hooks.rb:335 0.748
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
3:48.128
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.077
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.021
And Tor is ready 13.170
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.547
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.831
Given I shutdown Tails and wait for the computer to power off 9.499
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.350
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.325
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.228
When the network is plugged 0.017
And Tor is ready 9.939
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.043
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.735
Given I shutdown Tails and wait for the computer to power off 4.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.405
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.267
And the file system changes introduced in version 6.3~testoverlayfs are present 0.411
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.209
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.033
And Tor is ready 10.415
Then the Upgrader considers the system as up-to-date 10.582
# 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.439
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.444
After features/support/hooks.rb:335 0.851
After features/support/hooks.rb:104 0.019
Tags: @product @automatic_upgrade
20.944
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.538
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.249
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.783
After features/support/hooks.rb:335 0.844
After features/support/hooks.rb:104 0.000