Project Number Date
test_Tails_ISO_stable 6712 30 Sep 2026, 17:29

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.932 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:13.668
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 14.035
When I start Tails from USB drive "old" with network unplugged 55.478
Then the boot device has safe access rights 2.322
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 3.427
After features/support/hooks.rb:108 0.012
Tags: @product
1:26.855
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login 50.973
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 24.244
And I take note of which tps features are available 6.694
Then a Tails persistence partition exists on USB drive "old" 0.595
And I shutdown Tails and wait for the computer to power off 4.016
After features/support/hooks.rb:339 0.464
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.374
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.863
Then Tails is running from USB drive "old" 0.215
And all tps features are active 7.849
When I write some files expected to persist 1.283
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.298
And all persistent directories from the old Tails version have safe access rights 1.764
And I take note of which tps features are available 5.886
And I shutdown Tails and wait for the computer to power off 2.625
# 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.292
After features/support/hooks.rb:339 0.431
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.585
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.641
And I log in to a new session 12.476
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.651
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.294
Then the running Tails is installed on USB drive "to_upgrade" 19.065
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 1.913
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.481
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.447
Then all tps features from the old Tails version are active 1.301
And Tails is running from USB drive "to_upgrade" 0.219
And the boot device has safe access rights 2.415
And the expected persistent files created with the old Tails version are present in the filesystem 1.676
And all persistent directories from the old Tails version have safe access rights 2.311
After features/support/hooks.rb:339 0.760
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
4:6.625
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 9.801
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.203
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.303
When the network is plugged 0.028
And Tor is ready 14.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.839
Given I shutdown Tails and wait for the computer to power off 8.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.747
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 12.200
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.054
And Tor is ready 10.946
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.068
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.612
Given I shutdown Tails and wait for the computer to power off 4.005
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.762
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 12.679
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.037
And Tor is ready 10.131
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.814
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.452
After features/support/hooks.rb:339 1.168
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.342
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.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.946
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.917
After features/support/hooks.rb:339 0.813
After features/support/hooks.rb:108 0.000