Project Number Date
test_Tails_ISO_stable 6145 13 Feb 2026, 08:11

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:17.847 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:31.619
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.158
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.308
When I start Tails from USB drive "old" with network unplugged 56.287
Then the boot device has safe access rights 2.977
And Tails is running from USB drive "old" 0.278
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:331 3.564
After features/support/hooks.rb:100 0.009
Tags: @product
1:41.471
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:3.142
Then Tails is running from USB drive "old" 0.256
And I create a persistent partition 28.782
And I take note of which tps features are available 1.091
Then a Tails persistence partition exists on USB drive "old" 0.632
And I shutdown Tails and wait for the computer to power off 7.409
After features/support/hooks.rb:331 0.539
After features/support/hooks.rb:100 0.009
Tags: @product
1:44.159
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.639
Then Tails is running from USB drive "old" 0.262
And all tps features are active 1.756
When I write some files expected to persist 1.431
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 2.104
And I take note of which tps features are available 0.422
And I shutdown Tails and wait for the computer to power off 7.429
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.400
After features/support/hooks.rb:331 0.243
After features/support/hooks.rb:100 0.011
Tags: @product
2:33.908
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.712
And I log in to a new session 13.365
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.984
And I plug USB drive "to_upgrade" 2.708
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.711
Then the running Tails is installed on USB drive "to_upgrade" 20.012
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:331 2.261
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.301
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.155
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.517
Then all tps features from the old Tails version are active 1.336
And Tails is running from USB drive "to_upgrade" 0.267
And the boot device has safe access rights 2.817
And the expected persistent files created with the old Tails version are present in the filesystem 1.221
And all persistent directories from the old Tails version have safe access rights 1.984
After features/support/hooks.rb:331 0.563
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:3.012
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.878
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.052
And Tor is ready 13.160
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.738
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.196
Given I shutdown Tails and wait for the computer to power off 10.753
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.012
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.044
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.172
# 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.223
When the network is plugged 0.055
And Tor is ready 10.261
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.642
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.276
Given I shutdown Tails and wait for the computer to power off 7.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.879
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.024
And the file system changes introduced in version 6.3~testoverlayfs are present 0.443
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.165
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.075
And Tor is ready 11.618
Then the Upgrader considers the system as up-to-date 0.120
# 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.314
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.480
After features/support/hooks.rb:331 1.028
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
23.373
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.216
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.047
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 11.054
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.700
After features/support/hooks.rb:331 0.959
After features/support/hooks.rb:100 0.000