Project Number Date
test_Tails_ISO_stable 6160 23 Feb 2026, 12:00

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 14:14.293 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:34.657
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.298
When I start Tails from USB drive "old" with network unplugged 1:15.447
Then the boot device has safe access rights 3.028
And Tails is running from USB drive "old" 0.236
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.265
And I unplug USB drive "old" 0.161
After features/support/hooks.rb:331 3.899
After features/support/hooks.rb:100 0.007
Tags: @product
1:35.752
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:0.749
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 24.764
And I take note of which tps features are available 0.763
Then a Tails persistence partition exists on USB drive "old" 0.542
And I shutdown Tails and wait for the computer to power off 8.425
After features/support/hooks.rb:331 0.218
After features/support/hooks.rb:100 0.009
Tags: @product
1:33.063
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.109
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.111
Then Tails is running from USB drive "old" 0.350
And all tps features are active 1.151
When I write some files expected to persist 1.356
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 2.018
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 8.172
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.050
After features/support/hooks.rb:331 0.242
After features/support/hooks.rb:100 0.006
Tags: @product
2:23.092
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 without a persistent partition and stopped at Tails Greeter's login screen 8.588
And I log in to a new session 15.482
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.687
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.955
Then the running Tails is installed on USB drive "to_upgrade" 17.861
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:331 3.944
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.960
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.770
Then all tps features from the old Tails version are active 1.013
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 2.979
And the expected persistent files created with the old Tails version are present in the filesystem 1.612
And all persistent directories from the old Tails version have safe access rights 2.221
After features/support/hooks.rb:331 0.871
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
5:12.331
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.198
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
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.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.016
And Tor is ready 25.424
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.482
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.479
Given I shutdown Tails and wait for the computer to power off 19.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.015
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.213
And the file system changes introduced in version 6.2~testoverlayfs are present 0.256
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.148
# 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.184
When the network is plugged 0.016
And Tor is ready 21.795
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.434
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.061
Given I shutdown Tails and wait for the computer to power off 17.975
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.404
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.278
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.017
And Tor is ready 41.204
Then the Upgrader considers the system as up-to-date 0.142
# 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.841
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.422
After features/support/hooks.rb:331 0.772
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
42.436
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 21.148
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 20.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.435
After features/support/hooks.rb:331 1.064
After features/support/hooks.rb:100 0.000