Project Number Date
test_Tails_ISO_stable 6173 26 Feb 2026, 08:26

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 14:56.431 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:46.296
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 30.453
When I start Tails from USB drive "old" with network unplugged 1:10.810
Then the boot device has safe access rights 2.964
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.229
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:331 1.597
After features/support/hooks.rb:100 0.011
Tags: @product
1:37.314
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:0.407
Then Tails is running from USB drive "old" 0.295
And I create a persistent partition 26.936
And I take note of which tps features are available 1.190
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 7.527
After features/support/hooks.rb:331 0.705
After features/support/hooks.rb:100 0.010
Tags: @product
1:42.408
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.216
Then Tails is running from USB drive "old" 0.304
And all tps features are active 1.853
When I write some files expected to persist 1.505
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.191
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 7.422
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.684
After features/support/hooks.rb:331 0.461
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.622
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 without a persistent partition and stopped at Tails Greeter's login screen 12.827
And I log in to a new session 13.316
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.740
And I plug USB drive "to_upgrade" 2.437
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.955
Then the running Tails is installed on USB drive "to_upgrade" 18.953
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:331 2.913
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.866
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.296
Then all tps features from the old Tails version are active 1.747
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 2.968
And the expected persistent files created with the old Tails version are present in the filesystem 1.238
And all persistent directories from the old Tails version have safe access rights 2.125
After features/support/hooks.rb:331 1.077
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:27.645
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.872
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.053
And Tor is ready 25.279
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.594
Given I shutdown Tails and wait for the computer to power off 22.808
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:28.096
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.317
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.196
# 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.304
When the network is plugged 0.059
And Tor is ready 23.416
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.570
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.329
Given I shutdown Tails and wait for the computer to power off 17.795
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:27.127
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.309
And the file system changes introduced in version 6.3~testoverlayfs are present 0.401
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.047
And Tor is ready 22.761
Then the Upgrader considers the system as up-to-date 0.116
# 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 5.096
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.457
After features/support/hooks.rb:331 1.069
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
31.277
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 10.268
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 19.956
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.574
After features/support/hooks.rb:331 1.036
After features/support/hooks.rb:100 0.000