Project Number Date
test_Tails_ISO_web-release-7.14 2 29 Sep 2026, 18:13

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:56.081 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:9.614
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.396
When I start Tails from USB drive "old" with network unplugged 51.951
Then the boot device has safe access rights 2.471
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 1.256
After features/support/hooks.rb:108 0.007
Tags: @product
1:23.013
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 50.169
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 22.566
And I take note of which tps features are available 6.691
Then a Tails persistence partition exists on USB drive "old" 0.520
And I shutdown Tails and wait for the computer to power off 2.601
After features/support/hooks.rb:339 0.414
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.968
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.099
Then Tails is running from USB drive "old" 0.380
And all tps features are active 8.168
When I write some files expected to persist 1.308
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.147
And all persistence configuration files have safe access rights 0.251
And all persistent directories from the old Tails version have safe access rights 1.623
And I take note of which tps features are available 6.373
And I shutdown Tails and wait for the computer to power off 3.957
# 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.562
After features/support/hooks.rb:339 0.381
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.747
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.801
And I log in to a new session 13.473
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.156
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.843
Then the running Tails is installed on USB drive "to_upgrade" 19.991
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 0.654
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.127
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.163
Then all tps features from the old Tails version are active 1.145
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 2.652
And the expected persistent files created with the old Tails version are present in the filesystem 1.097
And all persistent directories from the old Tails version have safe access rights 1.779
After features/support/hooks.rb:339 0.522
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:44.053
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.847
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.375
When the network is plugged 0.041
And Tor is ready 12.458
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.011
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.611
Given I shutdown Tails and wait for the computer to power off 6.723
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.681
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 8.762
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.108
# 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.216
When the network is plugged 0.036
And Tor is ready 11.064
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.977
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.794
Given I shutdown Tails and wait for the computer to power off 5.079
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.156
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 10.781
And the file system changes introduced in version 6.3~testoverlayfs are present 0.278
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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.029
And Tor is ready 10.769
Then the Upgrader considers the system as up-to-date 0.087
# 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.402
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.477
After features/support/hooks.rb:339 1.643
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
32.557
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 21.507
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.036
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.035
And Tor is ready 9.771
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.945
After features/support/hooks.rb:339 0.680
After features/support/hooks.rb:108 0.000