Project Number Date
test_Tails_ISO_stable 6190 10 Mar 2026, 06:56

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:3.961 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.564
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.037
And I write an old version of the Tails USB image to disk "old" 15.577
When I start Tails from USB drive "old" with network unplugged 58.071
Then the boot device has safe access rights 2.972
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.253
And I unplug USB drive "old" 0.163
After features/support/hooks.rb:331 1.273
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 54.554
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 25.569
And I take note of which tps features are available 0.867
Then a Tails persistence partition exists on USB drive "old" 0.616
And I shutdown Tails and wait for the computer to power off 6.806
After features/support/hooks.rb:331 0.633
After features/support/hooks.rb:100 0.008
Tags: @product
1:23.965
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.670
Then Tails is running from USB drive "old" 0.243
And all tps features are active 1.130
When I write some files expected to persist 1.271
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.557
And all persistent directories from the old Tails version have safe access rights 1.986
And I take note of which tps features are available 0.228
And I shutdown Tails and wait for the computer to power off 4.423
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.193
After features/support/hooks.rb:331 0.403
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.997
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 8.770
And I log in to a new session 11.187
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.805
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.493
Then the running Tails is installed on USB drive "to_upgrade" 16.223
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:331 2.266
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.962
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.385
Then all tps features from the old Tails version are active 1.007
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.652
And the expected persistent files created with the old Tails version are present in the filesystem 1.450
And all persistent directories from the old Tails version have safe access rights 2.159
After features/support/hooks.rb:331 0.853
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:2.084
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.161
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.015
And Tor is ready 42.805
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.359
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.384
Given I shutdown Tails and wait for the computer to power off 19.083
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.716
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.202
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.228
When the network is plugged 0.015
And Tor is ready 21.629
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.359
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.845
Given I shutdown Tails and wait for the computer to power off 17.659
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.178
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.216
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.221
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.015
And Tor is ready 22.572
Then the Upgrader considers the system as up-to-date 0.137
# 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.829
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.352
After features/support/hooks.rb:331 0.909
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
26.622
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.477
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.088
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 18.391
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.359
After features/support/hooks.rb:331 0.587
After features/support/hooks.rb:100 0.000