Project Number Date
test_Tails_ISO_stable 6553 03 Aug 2026, 11:44

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:30.142 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
58.810
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.056
When I start Tails from USB drive "old" with network unplugged 41.412
Then the boot device has safe access rights 2.578
And Tails is running from USB drive "old" 0.249
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.774
After features/support/hooks.rb:108 0.031
Tags: @product
1:26.503
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 53.254
Then Tails is running from USB drive "old" 0.234
And I create a persistent partition 24.273
And I take note of which tps features are available 3.945
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 4.175
After features/support/hooks.rb:339 0.398
After features/support/hooks.rb:108 0.007
Tags: @product
1:32.127
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.860
Then Tails is running from USB drive "old" 0.256
And all tps features are active 5.028
When I write some files expected to persist 1.273
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 1.946
And I take note of which tps features are available 3.883
And I shutdown Tails and wait for the computer to power off 4.005
# 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.347
After features/support/hooks.rb:339 0.232
After features/support/hooks.rb:108 0.007
Tags: @product
2:8.877
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.783
And I log in to a new session 12.178
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.638
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.583
Then the running Tails is installed on USB drive "to_upgrade" 14.206
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 1.985
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.026
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:3.413
Then all tps features from the old Tails version are active 0.924
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.298
And the expected persistent files created with the old Tails version are present in the filesystem 1.208
And all persistent directories from the old Tails version have safe access rights 1.904
After features/support/hooks.rb:339 0.653
After features/support/hooks.rb:108 0.062
3:48.211
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 7.972
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.012
And Tor is ready 12.525
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.076
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.955
Given I shutdown Tails and wait for the computer to power off 7.190
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.025
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.051
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.247
When the network is plugged 0.018
And Tor is ready 9.903
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.152
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.031
Given I shutdown Tails and wait for the computer to power off 4.123
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.289
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 4.553
And the file system changes introduced in version 6.3~testoverlayfs are present 0.364
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.015
And Tor is ready 10.014
Then the Upgrader considers the system as up-to-date 10.510
# 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.119
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.360
After features/support/hooks.rb:339 0.732
After features/support/hooks.rb:108 0.011
25.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 with a persistent partition enabled and logged in 7.626
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
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.018
And Tor is ready 13.511
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.043
After features/support/hooks.rb:339 0.713
After features/support/hooks.rb:108 0.000