Project Number Date
test_Tails_ISO_stable 6750 16 Oct 2026, 11:26

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 10:36.654 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
53.702
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 13.373
When I start Tails from USB drive "old" with network unplugged 36.688
Then the boot device has safe access rights 1.830
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.833
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.565
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login 46.208
Then Tails is running from USB drive "old" 0.204
And I create a persistent partition 22.755
And I take note of which tps features are available 6.239
Then a Tails persistence partition exists on USB drive "old" 0.477
And I shutdown Tails and wait for the computer to power off 2.583
After features/support/hooks.rb:339 0.275
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.995
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.151
Then Tails is running from USB drive "old" 0.157
And all tps features are active 6.936
When I write some files expected to persist 1.171
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.125
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 1.661
And I take note of which tps features are available 6.057
And I shutdown Tails and wait for the computer to power off 3.938
# 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.416
After features/support/hooks.rb:339 0.275
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.533
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 8.200
And I log in to a new session 9.985
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.574
And I plug USB drive "to_upgrade" 2.205
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.946
Then the running Tails is installed on USB drive "to_upgrade" 17.389
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.734
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.479
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.950
Then all tps features from the old Tails version are active 1.013
And Tails is running from USB drive "to_upgrade" 0.148
And the boot device has safe access rights 1.980
And the expected persistent files created with the old Tails version are present in the filesystem 0.878
And all persistent directories from the old Tails version have safe access rights 1.435
After features/support/hooks.rb:339 0.744
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
3:21.489
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.081
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.161
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.251
When the network is plugged 0.023
And Tor is ready 12.263
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.923
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.739
Given I shutdown Tails and wait for the computer to power off 5.305
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.478
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.601
And the file system changes introduced in version 6.2~testoverlayfs are present 0.154
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.086
# 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.169
When the network is plugged 0.032
And Tor is ready 10.100
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.846
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.490
Given I shutdown Tails and wait for the computer to power off 4.040
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.369
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 7.600
And the file system changes introduced in version 6.3~testoverlayfs are present 0.289
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.091
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.045
And Tor is ready 9.966
Then the Upgrader considers the system as up-to-date 0.065
# 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 3.432
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.257
After features/support/hooks.rb:339 0.816
After features/support/hooks.rb:108 0.062
Tags: @product @automatic_upgrade
17.888
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.977
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
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.036
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 8.073
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.532
After features/support/hooks.rb:339 0.801
After features/support/hooks.rb:108 0.000