Project Number Date
test_Tails_ISO_stable 6401 24 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:4.369 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:6.437
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.016
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 12.920
When I start Tails from USB drive "old" with network unplugged 49.509
Then the boot device has safe access rights 2.210
And Tails is running from USB drive "old" 0.270
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.161
After features/support/hooks.rb:335 3.647
After features/support/hooks.rb:104 0.005
Tags: @product
1:24.333
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 51.190
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 24.102
And I take note of which tps features are available 0.347
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 7.797
After features/support/hooks.rb:335 0.518
After features/support/hooks.rb:104 0.006
Tags: @product
1:20.223
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.353
Then Tails is running from USB drive "old" 0.285
And all tps features are active 1.070
When I write some files expected to persist 1.241
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.135
And all persistence configuration files have safe access rights 0.275
And all persistent directories from the old Tails version have safe access rights 1.921
And I take note of which tps features are available 0.161
And I shutdown Tails and wait for the computer to power off 4.311
# 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.414
After features/support/hooks.rb:335 0.606
After features/support/hooks.rb:104 0.006
Tags: @product
2:9.566
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 7.552
And I log in to a new session 11.937
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.632
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.588
Then the running Tails is installed on USB drive "to_upgrade" 15.393
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:335 2.082
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.715
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.467
Then all tps features from the old Tails version are active 0.917
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.282
And the expected persistent files created with the old Tails version are present in the filesystem 0.995
And all persistent directories from the old Tails version have safe access rights 1.752
After features/support/hooks.rb:335 0.490
After features/support/hooks.rb:104 0.009
3:38.183
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.993
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.021
And Tor is ready 12.729
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.709
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.024
Given I shutdown Tails and wait for the computer to power off 10.899
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.849
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.229
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.182
When the network is plugged 0.014
And Tor is ready 13.166
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.968
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.097
Given I shutdown Tails and wait for the computer to power off 7.957
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.037
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.080
And the file system changes introduced in version 6.3~testoverlayfs are present 0.388
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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.013
And Tor is ready 10.439
Then the Upgrader considers the system as up-to-date 10.498
# 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.740
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:335 0.729
After features/support/hooks.rb:104 0.010
19.909
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.531
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
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.014
And Tor is ready 9.149
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.901
After features/support/hooks.rb:335 0.833
After features/support/hooks.rb:104 0.000