Project Number Date
test_Tails_ISO_stable 6431 06 Jun 2026, 11:34

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:27.887 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.892
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.329
When I start Tails from USB drive "old" with network unplugged 43.764
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:335 1.444
After features/support/hooks.rb:104 0.009
Tags: @product
1:28.516
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 53.390
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 25.525
And I take note of which tps features are available 0.371
Then a Tails persistence partition exists on USB drive "old" 0.579
And I shutdown Tails and wait for the computer to power off 8.344
After features/support/hooks.rb:335 0.354
After features/support/hooks.rb:104 0.008
Tags: @product
1:28.371
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.202
Then Tails is running from USB drive "old" 0.254
And all tps features are active 1.177
When I write some files expected to persist 1.439
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.334
And all persistent directories from the old Tails version have safe access rights 1.887
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 8.384
# 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.308
After features/support/hooks.rb:335 0.509
After features/support/hooks.rb:104 0.017
Tags: @product
2:12.159
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.501
And I log in to a new session 13.124
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.919
And I plug USB drive "to_upgrade" 2.274
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.369
Then the running Tails is installed on USB drive "to_upgrade" 15.698
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:335 2.662
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.061
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.183
Then all tps features from the old Tails version are active 1.241
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.764
And the expected persistent files created with the old Tails version are present in the filesystem 1.248
And all persistent directories from the old Tails version have safe access rights 2.284
After features/support/hooks.rb:335 0.635
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:45.104
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.123
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.016
And Tor is ready 12.699
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.109
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.814
Given I shutdown Tails and wait for the computer to power off 9.857
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.868
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.231
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.214
When the network is plugged 0.016
And Tor is ready 11.176
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.734
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.274
Given I shutdown Tails and wait for the computer to power off 8.285
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.855
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.305
And the file system changes introduced in version 6.3~testoverlayfs are present 0.385
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.177
When the network is plugged 0.033
And Tor is ready 11.115
Then the Upgrader considers the system as up-to-date 10.584
# 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.210
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.423
After features/support/hooks.rb:335 0.889
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
20.780
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.543
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.734
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.132
After features/support/hooks.rb:335 1.032
After features/support/hooks.rb:104 0.000