Project Number Date
test_Tails_ISO_stable 6116 03 Feb 2026, 19:31

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:32.013 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:50.784
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 31.691
When I start Tails from USB drive "old" with network unplugged 1:13.819
Then the boot device has safe access rights 3.109
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.168
After features/support/hooks.rb:331 4.248
After features/support/hooks.rb:100 0.079
Tags: @product
1:42.501
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.572
And I start Tails from USB drive "old" with network unplugged and I login 1:5.683
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 26.768
And I take note of which tps features are available 1.038
Then a Tails persistence partition exists on USB drive "old" 0.687
And I shutdown Tails and wait for the computer to power off 7.467
After features/support/hooks.rb:331 0.553
After features/support/hooks.rb:100 0.009
Tags: @product
1:43.386
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.547
Then Tails is running from USB drive "old" 0.311
And all tps features are active 1.734
When I write some files expected to persist 1.544
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.048
And I take note of which tps features are available 0.457
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.547
After features/support/hooks.rb:331 0.492
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.449
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 11.161
And I log in to a new session 13.035
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.020
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.527
Then the running Tails is installed on USB drive "to_upgrade" 19.889
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:331 4.069
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.809
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.574
Then all tps features from the old Tails version are active 1.371
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 2.849
And the expected persistent files created with the old Tails version are present in the filesystem 1.278
And all persistent directories from the old Tails version have safe access rights 2.249
After features/support/hooks.rb:331 0.959
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:4.795
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 12.178
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.048
And Tor is ready 13.678
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.646
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.914
Given I shutdown Tails and wait for the computer to power off 12.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.829
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.904
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.220
When the network is plugged 0.063
And Tor is ready 12.859
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.555
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.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.287
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.907
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.061
# 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.195
When the network is plugged 0.057
And Tor is ready 12.021
Then the Upgrader considers the system as up-to-date 0.131
# 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.197
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.478
After features/support/hooks.rb:331 0.807
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
22.286
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 10.245
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 10.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.585
After features/support/hooks.rb:331 1.032
After features/support/hooks.rb:100 0.000