Project Number Date
test_Tails_ISO_stable 6740 12 Oct 2026, 16:06

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:43.204 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:1.350
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 14.064
When I start Tails from USB drive "old" with network unplugged 42.958
Then the boot device has safe access rights 2.446
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.746
After features/support/hooks.rb:108 0.007
Tags: @product
1:27.962
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.127
And I start Tails from USB drive "old" with network unplugged and I login 49.948
Then Tails is running from USB drive "old" 0.222
And I create a persistent partition 24.716
And I take note of which tps features are available 8.296
Then a Tails persistence partition exists on USB drive "old" 0.482
And I shutdown Tails and wait for the computer to power off 4.169
After features/support/hooks.rb:339 0.386
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.468
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.053
Then Tails is running from USB drive "old" 0.187
And all tps features are active 9.985
When I write some files expected to persist 1.334
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 1.835
And I take note of which tps features are available 6.882
And I shutdown Tails and wait for the computer to power off 3.095
# 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.441
After features/support/hooks.rb:339 0.337
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.249
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 8.490
And I log in to a new session 11.991
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.795
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.985
Then the running Tails is installed on USB drive "to_upgrade" 19.539
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.695
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.744
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.508
Then all tps features from the old Tails version are active 1.607
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 2.953
And the expected persistent files created with the old Tails version are present in the filesystem 1.372
And all persistent directories from the old Tails version have safe access rights 1.840
After features/support/hooks.rb:339 1.015
After features/support/hooks.rb:108 0.027
Tags: @product @automatic_upgrade
3:43.448
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 8.317
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.360
When the network is plugged 0.029
And Tor is ready 13.707
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.304
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.458
Given I shutdown Tails and wait for the computer to power off 5.514
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.600
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.385
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.190
When the network is plugged 0.026
And Tor is ready 10.842
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.329
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.814
Given I shutdown Tails and wait for the computer to power off 2.661
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.495
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.336
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
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.090
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.606
And Tor is ready 11.436
Then the Upgrader considers the system as up-to-date 0.106
# 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.717
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.940
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
19.980
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.178
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 11.011
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.302
After features/support/hooks.rb:339 0.744
After features/support/hooks.rb:108 0.000