Project Number Date
test_Tails_ISO_stable 6031 02 Jan 2026, 09:37

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 16:5.134 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:49.891
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 34.423
When I start Tails from USB drive "old" with network unplugged 1:9.923
Then the boot device has safe access rights 3.257
And Tails is running from USB drive "old" 0.384
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.264
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:331 3.775
After features/support/hooks.rb:100 0.035
Tags: @product
1:52.850
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login 1:8.030
Then Tails is running from USB drive "old" 0.708
And I create a persistent partition 33.363
And I take note of which tps features are available 1.444
Then a Tails persistence partition exists on USB drive "old" 0.702
And I shutdown Tails and wait for the computer to power off 8.372
After features/support/hooks.rb:331 0.633
After features/support/hooks.rb:100 0.011
Tags: @product
1:58.015
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:21.701
Then Tails is running from USB drive "old" 0.344
And all tps features are active 2.171
When I write some files expected to persist 2.462
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
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.521
And I take note of which tps features are available 0.550
And I shutdown Tails and wait for the computer to power off 8.003
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.337
After features/support/hooks.rb:331 0.592
After features/support/hooks.rb:100 0.010
Tags: @product
2:44.711
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 14.930
And I log in to a new session 17.816
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.815
And I plug USB drive "to_upgrade" 2.662
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.196
Then the running Tails is installed on USB drive "to_upgrade" 21.840
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:331 4.338
After features/support/hooks.rb:100 0.000
Tags: @product
1:33.495
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 0.308
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:23.667
Then all tps features from the old Tails version are active 1.955
And Tails is running from USB drive "to_upgrade" 0.441
And the boot device has safe access rights 3.300
And the expected persistent files created with the old Tails version are present in the filesystem 1.408
And all persistent directories from the old Tails version have safe access rights 2.413
After features/support/hooks.rb:331 1.215
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:11.067
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 with a persistent partition enabled and logged in 14.046
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
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.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.487
When the network is plugged 0.059
And Tor is ready 44.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.646
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.095
Given I shutdown Tails and wait for the computer to power off 10.954
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:27.237
Then Tails is running version 6.2~testoverlayfs 0.071
And all tps features are active 2.375
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.166
# 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.060
And Tor is ready 10.909
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.318
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.566
Given I shutdown Tails and wait for the computer to power off 7.791
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.441
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.116
And the file system changes introduced in version 6.3~testoverlayfs are present 0.395
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.278
When the network is plugged 0.090
And Tor is ready 11.614
Then the Upgrader considers the system as up-to-date 10.722
# 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.814
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.616
After features/support/hooks.rb:331 0.905
After features/support/hooks.rb:100 0.067
Tags: @product @automatic_upgrade
55.101
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.294
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 42.506
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.697
After features/support/hooks.rb:331 0.891
After features/support/hooks.rb:100 0.000