Project Number Date
test_Tails_ISO_stable 6123 05 Feb 2026, 15:22

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 15:13.773 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
2:1.306
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 34.419
When I start Tails from USB drive "old" with network unplugged 1:20.956
Then the boot device has safe access rights 3.586
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.379
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:331 4.277
After features/support/hooks.rb:100 0.011
Tags: @product
1:51.009
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.302
And I start Tails from USB drive "old" with network unplugged and I login 1:10.587
Then Tails is running from USB drive "old" 0.692
And I create a persistent partition 29.059
And I take note of which tps features are available 1.180
Then a Tails persistence partition exists on USB drive "old" 0.681
And I shutdown Tails and wait for the computer to power off 8.506
After features/support/hooks.rb:331 0.524
After features/support/hooks.rb:100 0.010
Tags: @product
1:56.311
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:19.887
Then Tails is running from USB drive "old" 0.641
And all tps features are active 1.895
When I write some files expected to persist 2.027
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.449
And all persistent directories from the old Tails version have safe access rights 2.301
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 7.692
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 20.473
After features/support/hooks.rb:331 0.344
After features/support/hooks.rb:100 0.026
Tags: @product
2:42.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.241
And I log in to a new session 15.314
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.302
And I plug USB drive "to_upgrade" 2.877
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.176
Then the running Tails is installed on USB drive "to_upgrade" 23.107
And I unplug USB drive "to_upgrade" 0.263
And I unplug USB drive "__internal" 0.289
After features/support/hooks.rb:331 2.451
After features/support/hooks.rb:100 0.000
Tags: @product
1:33.811
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:24.678
Then all tps features from the old Tails version are active 1.735
And Tails is running from USB drive "to_upgrade" 0.262
And the boot device has safe access rights 3.130
And the expected persistent files created with the old Tails version are present in the filesystem 1.529
And all persistent directories from the old Tails version have safe access rights 2.287
After features/support/hooks.rb:331 1.056
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
4:43.460
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 13.787
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
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.396
When the network is plugged 0.048
And Tor is ready 14.869
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.678
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.559
Given I shutdown Tails and wait for the computer to power off 11.970
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:32.080
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.710
And the file system changes introduced in version 6.2~testoverlayfs are present 0.378
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.201
# 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.258
When the network is plugged 0.065
And Tor is ready 13.301
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.801
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.828
Given I shutdown Tails and wait for the computer to power off 7.701
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.185
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.492
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.191
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.331
When the network is plugged 0.067
And Tor is ready 12.192
Then the Upgrader considers the system as up-to-date 0.169
# 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 7.221
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.536
After features/support/hooks.rb:331 0.873
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
25.300
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 11.362
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 11.630
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.843
After features/support/hooks.rb:331 1.053
After features/support/hooks.rb:100 0.000