Project Number Date
test_Tails_ISO_devel 4582 01 Sep 2026, 19:41

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:58.800 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:12.784
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.945
When I start Tails from USB drive "old" with network unplugged 53.767
Then the boot device has safe access rights 3.207
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.783
After features/support/hooks.rb:108 0.007
Tags: @product
1:27.019
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login 51.052
Then Tails is running from USB drive "old" 0.438
And I create a persistent partition 25.011
And I take note of which tps features are available 7.143
Then a Tails persistence partition exists on USB drive "old" 0.545
And I shutdown Tails and wait for the computer to power off 2.726
After features/support/hooks.rb:339 0.320
After features/support/hooks.rb:108 0.008
Tags: @product
1:38.208
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.323
Then Tails is running from USB drive "old" 0.300
And all tps features are active 7.894
When I write some files expected to persist 1.150
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.271
And all persistent directories from the old Tails version have safe access rights 1.694
And I take note of which tps features are available 6.337
And I shutdown Tails and wait for the computer to power off 4.225
# 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.734
After features/support/hooks.rb:339 0.139
After features/support/hooks.rb:108 0.005
Tags: @product
2:15.339
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.348
And I log in to a new session 12.024
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.700
And I plug USB drive "to_upgrade" 2.276
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.729
Then the running Tails is installed on USB drive "to_upgrade" 19.998
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 3.779
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.378
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.626
Then all tps features from the old Tails version are active 1.249
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 3.272
And the expected persistent files created with the old Tails version are present in the filesystem 1.520
And all persistent directories from the old Tails version have safe access rights 2.366
After features/support/hooks.rb:339 0.807
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
3:45.956
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.750
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.185
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.030
And Tor is ready 11.661
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.609
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.306
Given I shutdown Tails and wait for the computer to power off 6.950
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.139
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.002
And the file system changes introduced in version 6.2~testoverlayfs are present 0.212
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.239
When the network is plugged 0.028
And Tor is ready 10.240
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.456
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.120
Given I shutdown Tails and wait for the computer to power off 4.413
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.312
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.087
And the file system changes introduced in version 6.3~testoverlayfs are present 0.392
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.025
And Tor is ready 10.316
Then the Upgrader considers the system as up-to-date 0.096
# 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.757
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.271
After features/support/hooks.rb:339 1.809
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
21.113
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.647
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.023
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.028
After features/support/hooks.rb:339 0.632
After features/support/hooks.rb:108 0.000