Project Number Date
test_Tails_ISO_stable 6268 06 Apr 2026, 17:56

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 13:24.526 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:30.703
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
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" 14.237
When I start Tails from USB drive "old" with network unplugged 1:11.751
Then the boot device has safe access rights 2.940
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:331 1.662
After features/support/hooks.rb:100 0.008
Tags: @product
1:27.459
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 54.420
Then Tails is running from USB drive "old" 0.274
And I create a persistent partition 24.376
And I take note of which tps features are available 0.774
Then a Tails persistence partition exists on USB drive "old" 0.667
And I shutdown Tails and wait for the computer to power off 6.875
After features/support/hooks.rb:331 0.389
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.866
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.575
Then Tails is running from USB drive "old" 0.266
And all tps features are active 1.084
When I write some files expected to persist 1.191
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 2.087
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.156
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.622
After features/support/hooks.rb:331 0.511
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.991
And I log in to a new session 21.490
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.842
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.253
Then the running Tails is installed on USB drive "to_upgrade" 16.833
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 0.813
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.366
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.553
Then all tps features from the old Tails version are active 0.928
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.450
And the expected persistent files created with the old Tails version are present in the filesystem 1.114
And all persistent directories from the old Tails version have safe access rights 2.022
After features/support/hooks.rb:331 0.909
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:49.456
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.988
And no SquashFS delta is installed 0.215
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.354
When the network is plugged 0.016
And Tor is ready 30.283
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.363
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.701
Given I shutdown Tails and wait for the computer to power off 16.985
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.906
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.292
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.273
When the network is plugged 0.019
And Tor is ready 20.472
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.402
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.566
Given I shutdown Tails and wait for the computer to power off 17.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.196
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 1.226
And the file system changes introduced in version 6.3~testoverlayfs are present 0.361
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.019
And Tor is ready 20.664
Then the Upgrader considers the system as up-to-date 0.094
# 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.377
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:331 1.038
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
28.756
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.793
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 20.162
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.384
After features/support/hooks.rb:331 1.035
After features/support/hooks.rb:100 0.000