Project Number Date
test_Tails_ISO_stable 6395 21 May 2026, 11:36

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:59.262 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:13.110
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.336
When I start Tails from USB drive "old" with network unplugged 53.677
Then the boot device has safe access rights 3.205
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:335 1.412
After features/support/hooks.rb:104 0.006
Tags: @product
1:31.728
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 57.047
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 25.125
And I take note of which tps features are available 0.550
Then a Tails persistence partition exists on USB drive "old" 0.595
And I shutdown Tails and wait for the computer to power off 8.064
After features/support/hooks.rb:335 0.594
After features/support/hooks.rb:104 0.006
Tags: @product
1:30.112
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.412
Then Tails is running from USB drive "old" 0.300
And all tps features are active 1.473
When I write some files expected to persist 1.329
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.311
And all persistence configuration files have safe access rights 0.325
And all persistent directories from the old Tails version have safe access rights 1.887
And I take note of which tps features are available 0.170
And I shutdown Tails and wait for the computer to power off 4.241
# 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" 12.597
After features/support/hooks.rb:335 0.360
After features/support/hooks.rb:104 0.007
Tags: @product
2:14.913
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 7.967
And I log in to a new session 13.602
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.776
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.982
Then the running Tails is installed on USB drive "to_upgrade" 17.990
And I unplug USB drive "to_upgrade" 0.174
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:335 2.153
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.606
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.997
Then all tps features from the old Tails version are active 1.005
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.750
And the expected persistent files created with the old Tails version are present in the filesystem 1.257
And all persistent directories from the old Tails version have safe access rights 2.264
After features/support/hooks.rb:335 0.828
After features/support/hooks.rb:104 0.020
Tags: @product @automatic_upgrade
3:55.798
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.065
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.018
And Tor is ready 13.868
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.997
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.015
Given I shutdown Tails and wait for the computer to power off 10.136
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.960
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.103
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# 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.197
When the network is plugged 0.020
And Tor is ready 11.630
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.612
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.045
Given I shutdown Tails and wait for the computer to power off 8.086
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.214
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.494
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.017
And Tor is ready 10.904
Then the Upgrader considers the system as up-to-date 10.526
# 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.780
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.397
After features/support/hooks.rb:335 0.814
After features/support/hooks.rb:104 0.015
Tags: @product @automatic_upgrade
20.990
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.673
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
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.014
And Tor is ready 10.301
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.682
After features/support/hooks.rb:335 0.764
After features/support/hooks.rb:104 0.000