Project Number Date
test_Tails_ISO_stable 6158 21 Feb 2026, 11:42

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 12:28.750 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:10.271
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.469
When I start Tails from USB drive "old" with network unplugged 52.185
Then the boot device has safe access rights 2.848
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 1.615
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.152
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 55.104
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 24.985
And I take note of which tps features are available 0.740
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 8.469
After features/support/hooks.rb:331 0.242
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.227
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.653
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.238
When I write some files expected to persist 1.320
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.279
And all persistent directories from the old Tails version have safe access rights 1.952
And I take note of which tps features are available 0.163
And I shutdown Tails and wait for the computer to power off 2.631
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.474
After features/support/hooks.rb:331 0.602
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.081
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.572
And I log in to a new session 12.072
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.854
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.242
Then the running Tails is installed on USB drive "to_upgrade" 14.783
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 3.668
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.629
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.426
Then all tps features from the old Tails version are active 1.008
And Tails is running from USB drive "to_upgrade" 0.292
And the boot device has safe access rights 2.891
And the expected persistent files created with the old Tails version are present in the filesystem 1.100
And all persistent directories from the old Tails version have safe access rights 1.837
After features/support/hooks.rb:331 0.605
After features/support/hooks.rb:100 0.006
4:37.393
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.360
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
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.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.015
And Tor is ready 20.569
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.414
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.648
Given I shutdown Tails and wait for the computer to power off 18.811
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.598
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.227
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.202
# 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.186
When the network is plugged 0.019
And Tor is ready 21.550
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.761
Given I shutdown Tails and wait for the computer to power off 17.202
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.659
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.182
And the file system changes introduced in version 6.3~testoverlayfs are present 0.397
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.014
And Tor is ready 20.689
Then the Upgrader considers the system as up-to-date 0.119
# 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.351
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.379
After features/support/hooks.rb:331 1.046
After features/support/hooks.rb:100 0.010
24.993
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.295
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 16.860
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.383
After features/support/hooks.rb:331 0.951
After features/support/hooks.rb:100 0.000