Project Number Date
test_Tails_ISO_stable 6551 01 Aug 2026, 11:49

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:51.564 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:7.347
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.705
When I start Tails from USB drive "old" with network unplugged 48.779
Then the boot device has safe access rights 3.022
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 3.785
After features/support/hooks.rb:108 0.034
Tags: @product
1:29.167
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 55.195
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 24.428
And I take note of which tps features are available 4.605
Then a Tails persistence partition exists on USB drive "old" 0.590
And I shutdown Tails and wait for the computer to power off 4.018
After features/support/hooks.rb:339 0.235
After features/support/hooks.rb:108 0.007
Tags: @product
1:35.523
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.664
Then Tails is running from USB drive "old" 0.291
And all tps features are active 5.183
When I write some files expected to persist 1.336
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.054
And I take note of which tps features are available 3.767
And I shutdown Tails and wait for the computer to power off 4.037
# 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.537
After features/support/hooks.rb:339 0.307
After features/support/hooks.rb:108 0.007
Tags: @product
2:10.200
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 without a persistent partition and stopped at Tails Greeter's login screen 7.631
And I log in to a new session 12.826
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.747
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.848
Then the running Tails is installed on USB drive "to_upgrade" 14.623
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:339 6.953
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.333
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.938
Then all tps features from the old Tails version are active 1.093
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 2.731
And the expected persistent files created with the old Tails version are present in the filesystem 1.155
And all persistent directories from the old Tails version have safe access rights 2.068
After features/support/hooks.rb:339 0.897
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:53.911
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.072
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.016
And Tor is ready 13.055
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.755
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.455
Given I shutdown Tails and wait for the computer to power off 6.973
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.001
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.829
And the file system changes introduced in version 6.2~testoverlayfs are present 0.227
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# 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.219
When the network is plugged 0.016
And Tor is ready 10.389
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.876
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.945
Given I shutdown Tails and wait for the computer to power off 4.050
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.143
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.097
And the file system changes introduced in version 6.3~testoverlayfs are present 0.381
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.017
And Tor is ready 11.649
Then the Upgrader considers the system as up-to-date 10.591
# 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.279
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.377
After features/support/hooks.rb:339 1.077
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
20.080
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 7.694
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.122
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.885
After features/support/hooks.rb:339 0.906
After features/support/hooks.rb:108 0.000