Project Number Date
test_Tails_ISO_stable 6513 20 Jul 2026, 17:34

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:8.848 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.995
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.052
When I start Tails from USB drive "old" with network unplugged 52.457
Then the boot device has safe access rights 2.744
And Tails is running from USB drive "old" 0.236
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:339 3.650
After features/support/hooks.rb:108 0.013
Tags: @product
1:33.555
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 55.481
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 24.520
And I take note of which tps features are available 4.267
Then a Tails persistence partition exists on USB drive "old" 0.700
And I shutdown Tails and wait for the computer to power off 8.236
After features/support/hooks.rb:339 0.315
After features/support/hooks.rb:108 0.007
Tags: @product
1:41.178
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.946
Then Tails is running from USB drive "old" 0.256
And all tps features are active 5.079
When I write some files expected to persist 1.387
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.370
And all persistent directories from the old Tails version have safe access rights 2.372
And I take note of which tps features are available 4.381
And I shutdown Tails and wait for the computer to power off 8.355
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.789
After features/support/hooks.rb:339 0.217
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.005
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 7.660
And I log in to a new session 14.523
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.796
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.083
Then the running Tails is installed on USB drive "to_upgrade" 15.387
And I unplug USB drive "to_upgrade" 0.168
And I unplug USB drive "__internal" 0.164
After features/support/hooks.rb:339 1.969
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.482
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.589
Then all tps features from the old Tails version are active 1.039
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.465
And the expected persistent files created with the old Tails version are present in the filesystem 1.086
And all persistent directories from the old Tails version have safe access rights 2.012
After features/support/hooks.rb:339 0.791
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:54.513
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.274
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.405
When the network is plugged 0.021
And Tor is ready 13.893
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.555
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.032
Given I shutdown Tails and wait for the computer to power off 6.791
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.190
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.506
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.208
When the network is plugged 0.017
And Tor is ready 10.077
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.730
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.574
Given I shutdown Tails and wait for the computer to power off 3.962
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.805
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 5.729
And the file system changes introduced in version 6.3~testoverlayfs are present 0.325
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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.013
And Tor is ready 10.693
Then the Upgrader considers the system as up-to-date 10.580
# 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.218
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:339 0.979
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.116
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.539
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
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.027
And Tor is ready 10.229
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.941
After features/support/hooks.rb:339 0.635
After features/support/hooks.rb:108 0.000