Project Number Date
test_Tails_ISO_stable 6442 12 Jun 2026, 11: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 12:12.007 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:9.902
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.149
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 13.653
When I start Tails from USB drive "old" with network unplugged 51.797
Then the boot device has safe access rights 2.503
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.723
After features/support/hooks.rb:108 0.018
Tags: @product
1:31.566
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.146
And I start Tails from USB drive "old" with network unplugged and I login 54.706
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 24.458
And I take note of which tps features are available 4.455
Then a Tails persistence partition exists on USB drive "old" 0.555
And I shutdown Tails and wait for the computer to power off 7.004
After features/support/hooks.rb:339 0.310
After features/support/hooks.rb:108 0.021
Tags: @product
1:36.744
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.108
Then Tails is running from USB drive "old" 0.289
And all tps features are active 5.340
When I write some files expected to persist 1.307
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 2.024
And I take note of which tps features are available 4.047
And I shutdown Tails and wait for the computer to power off 4.523
# 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.432
After features/support/hooks.rb:339 0.156
After features/support/hooks.rb:108 0.018
Tags: @product
2:12.476
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.264
And I log in to a new session 13.202
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.730
And I plug USB drive "to_upgrade" 2.272
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.789
Then the running Tails is installed on USB drive "to_upgrade" 15.908
And I unplug USB drive "to_upgrade" 0.163
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 2.036
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.229
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.158
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.103
Then all tps features from the old Tails version are active 0.856
And Tails is running from USB drive "to_upgrade" 0.254
And the boot device has safe access rights 2.878
And the expected persistent files created with the old Tails version are present in the filesystem 1.098
And all persistent directories from the old Tails version have safe access rights 1.880
After features/support/hooks.rb:339 0.985
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
4:4.222
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.522
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.357
When the network is plugged 0.015
And Tor is ready 13.875
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.923
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.451
Given I shutdown Tails and wait for the computer to power off 9.849
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.459
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.196
And the file system changes introduced in version 6.2~testoverlayfs are present 0.249
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.249
When the network is plugged 0.024
And Tor is ready 9.630
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.795
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.188
Given I shutdown Tails and wait for the computer to power off 8.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.976
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.772
And the file system changes introduced in version 6.3~testoverlayfs are present 0.323
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.018
And Tor is ready 9.958
Then the Upgrader considers the system as up-to-date 10.577
# 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.701
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:339 0.715
After features/support/hooks.rb:108 0.046
Tags: @product @automatic_upgrade
21.865
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.808
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.596
After features/support/hooks.rb:339 0.892
After features/support/hooks.rb:108 0.000