Project Number Date
test_Tails_ISO_stable 6496 11 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:39.114 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:2.626
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.109
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.979
When I start Tails from USB drive "old" with network unplugged 45.484
Then the boot device has safe access rights 2.362
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:339 1.366
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.049
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 51.404
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 24.728
And I take note of which tps features are available 4.157
Then a Tails persistence partition exists on USB drive "old" 0.583
And I shutdown Tails and wait for the computer to power off 7.877
After features/support/hooks.rb:339 0.345
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.063
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.246
Then Tails is running from USB drive "old" 0.261
And all tps features are active 5.235
When I write some files expected to persist 1.388
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 1.945
And I take note of which tps features are available 3.824
And I shutdown Tails and wait for the computer to power off 7.790
# 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.820
After features/support/hooks.rb:339 0.288
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.387
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.794
And I log in to a new session 12.694
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.678
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.038
Then the running Tails is installed on USB drive "to_upgrade" 14.691
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.073
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.109
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.414
Then all tps features from the old Tails version are active 0.988
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.486
And the expected persistent files created with the old Tails version are present in the filesystem 1.112
And all persistent directories from the old Tails version have safe access rights 1.797
After features/support/hooks.rb:339 0.546
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:50.194
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.231
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.014
And Tor is ready 12.894
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.778
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.100
Given I shutdown Tails and wait for the computer to power off 9.277
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.025
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.153
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# 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.243
When the network is plugged 0.025
And Tor is ready 9.696
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.138
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.203
Given I shutdown Tails and wait for the computer to power off 7.975
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.380
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.753
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.040
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.014
And Tor is ready 9.808
Then the Upgrader considers the system as up-to-date 10.569
# 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.309
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.404
After features/support/hooks.rb:339 0.761
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
20.682
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.482
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.014
And Tor is ready 10.215
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.622
After features/support/hooks.rb:339 1.052
After features/support/hooks.rb:108 0.000