Project Number Date
test_Tails_ISO_stable 6152 17 Feb 2026, 14:10

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 12:23.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:18.890
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 15.420
When I start Tails from USB drive "old" with network unplugged 57.433
Then the boot device has safe access rights 3.920
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.369
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:331 1.992
After features/support/hooks.rb:100 0.006
Tags: @product
1:36.570
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.124
And I start Tails from USB drive "old" with network unplugged and I login 59.787
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 25.736
And I take note of which tps features are available 0.844
Then a Tails persistence partition exists on USB drive "old" 0.620
And I shutdown Tails and wait for the computer to power off 9.128
After features/support/hooks.rb:331 0.440
After features/support/hooks.rb:100 0.010
Tags: @product
1:36.437
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.786
Then Tails is running from USB drive "old" 0.230
And all tps features are active 1.173
When I write some files expected to persist 1.452
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 2.115
And I take note of which tps features are available 0.188
And I shutdown Tails and wait for the computer to power off 8.538
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.143
After features/support/hooks.rb:331 0.438
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.450
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.131
And I log in to a new session 13.124
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.055
And I plug USB drive "to_upgrade" 2.289
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.989
Then the running Tails is installed on USB drive "to_upgrade" 17.565
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:331 3.040
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.672
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.375
Then all tps features from the old Tails version are active 1.211
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 2.917
And the expected persistent files created with the old Tails version are present in the filesystem 1.263
And all persistent directories from the old Tails version have safe access rights 2.438
After features/support/hooks.rb:331 0.655
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
3:57.831
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 with a persistent partition enabled and logged in 9.659
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.018
And Tor is ready 13.784
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.240
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.008
Given I shutdown Tails and wait for the computer to power off 9.742
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.309
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.340
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.017
And Tor is ready 13.287
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.662
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.544
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 1:7.852
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.479
And the file system changes introduced in version 6.3~testoverlayfs are present 0.439
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.036
And Tor is ready 10.768
Then the Upgrader considers the system as up-to-date 10.541
# 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.118
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.416
After features/support/hooks.rb:331 1.120
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
20.408
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 7.697
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.273
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.079
After features/support/hooks.rb:331 0.832
After features/support/hooks.rb:100 0.000