Project Number Date
test_Tails_ISO_devel 4399 16 May 2026, 11:00

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 10:44.496 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
57.338
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 12.781
When I start Tails from USB drive "old" with network unplugged 40.260
Then the boot device has safe access rights 2.567
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:335 1.366
After features/support/hooks.rb:104 0.006
Tags: @product
1:21.193
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 51.866
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 23.984
And I take note of which tps features are available 0.325
Then a Tails persistence partition exists on USB drive "old" 0.550
And I shutdown Tails and wait for the computer to power off 4.186
After features/support/hooks.rb:335 0.197
After features/support/hooks.rb:104 0.007
Tags: @product
1:19.216
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.009
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.957
Then Tails is running from USB drive "old" 0.337
And all tps features are active 1.100
When I write some files expected to persist 1.247
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 1.758
And I take note of which tps features are available 0.187
And I shutdown Tails and wait for the computer to power off 2.754
# 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.313
After features/support/hooks.rb:335 0.158
After features/support/hooks.rb:104 0.006
Tags: @product
2:8.521
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 without a persistent partition and stopped at Tails Greeter's login screen 8.124
And I log in to a new session 11.392
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.668
And I plug USB drive "to_upgrade" 2.223
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.751
Then the running Tails is installed on USB drive "to_upgrade" 15.054
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.172
After features/support/hooks.rb:335 1.996
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.867
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.374
Then all tps features from the old Tails version are active 0.915
And Tails is running from USB drive "to_upgrade" 0.211
And the boot device has safe access rights 2.433
And the expected persistent files created with the old Tails version are present in the filesystem 1.023
And all persistent directories from the old Tails version have safe access rights 1.860
After features/support/hooks.rb:335 0.864
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:33.463
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 with a persistent partition enabled and logged in 8.099
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.354
When the network is plugged 0.020
And Tor is ready 12.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.107
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.315
Given I shutdown Tails and wait for the computer to power off 9.284
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.660
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.090
And the file system changes introduced in version 6.2~testoverlayfs are present 0.253
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.232
When the network is plugged 0.018
And Tor is ready 11.305
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.346
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.801
Given I shutdown Tails and wait for the computer to power off 8.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.648
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.068
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.045
# 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.182
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.014
And Tor is ready 9.591
Then the Upgrader considers the system as up-to-date 10.506
# 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.786
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.327
After features/support/hooks.rb:335 0.903
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
18.894
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.018
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.857
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.698
After features/support/hooks.rb:335 0.874
After features/support/hooks.rb:104 0.000