Project Number Date
test_Tails_ISO_stable 6487 02 Jul 2026, 11: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 11:31.412 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:4.433
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 12.961
When I start Tails from USB drive "old" with network unplugged 47.277
Then the boot device has safe access rights 2.507
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 1.160
After features/support/hooks.rb:108 0.007
Tags: @product
1:28.300
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 50.636
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 24.608
And I take note of which tps features are available 3.965
Then a Tails persistence partition exists on USB drive "old" 0.549
And I shutdown Tails and wait for the computer to power off 8.240
After features/support/hooks.rb:339 0.573
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.104
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.044
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.329
Then Tails is running from USB drive "old" 0.224
And all tps features are active 4.742
When I write some files expected to persist 1.256
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 1.803
And I take note of which tps features are available 3.540
And I shutdown Tails and wait for the computer to power off 7.901
# 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" 11.775
After features/support/hooks.rb:339 0.250
After features/support/hooks.rb:108 0.006
Tags: @product
2:7.502
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.530
And I log in to a new session 11.058
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.706
And I plug USB drive "to_upgrade" 2.194
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.111
Then the running Tails is installed on USB drive "to_upgrade" 14.614
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 2.063
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.434
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.140
Then all tps features from the old Tails version are active 0.946
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.319
And the expected persistent files created with the old Tails version are present in the filesystem 1.050
And all persistent directories from the old Tails version have safe access rights 1.700
After features/support/hooks.rb:339 0.809
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:47.493
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 8.116
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.016
And Tor is ready 12.993
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.700
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.497
Given I shutdown Tails and wait for the computer to power off 9.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.658
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.790
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.197
When the network is plugged 0.034
And Tor is ready 9.799
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.664
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.744
Given I shutdown Tails and wait for the computer to power off 7.912
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.215
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.461
And the file system changes introduced in version 6.3~testoverlayfs are present 0.341
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.017
And Tor is ready 10.116
Then the Upgrader considers the system as up-to-date 10.471
# 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.185
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.856
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.144
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.362
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.465
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.958
After features/support/hooks.rb:339 0.625
After features/support/hooks.rb:108 0.000