Project Number Date
test_Tails_ISO_stable 6380 15 May 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 12:0.965 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:3.929
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.426
When I start Tails from USB drive "old" with network unplugged 44.962
Then the boot device has safe access rights 2.694
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:335 1.215
After features/support/hooks.rb:104 0.007
Tags: @product
1:33.303
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 56.828
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 27.100
And I take note of which tps features are available 0.378
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 8.155
After features/support/hooks.rb:335 0.620
After features/support/hooks.rb:104 0.006
Tags: @product
1:35.322
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.025
Then Tails is running from USB drive "old" 0.347
And all tps features are active 1.290
When I write some files expected to persist 1.746
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 2.308
And I take note of which tps features are available 0.178
And I shutdown Tails and wait for the computer to power off 8.418
# 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" 13.348
After features/support/hooks.rb:335 0.621
After features/support/hooks.rb:104 0.009
Tags: @product
2:14.296
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.243
And I log in to a new session 14.074
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.905
And I plug USB drive "to_upgrade" 2.289
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.411
Then the running Tails is installed on USB drive "to_upgrade" 16.056
And I unplug USB drive "to_upgrade" 0.172
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:335 2.338
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.264
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.516
Then all tps features from the old Tails version are active 1.137
And Tails is running from USB drive "to_upgrade" 0.265
And the boot device has safe access rights 2.675
And the expected persistent files created with the old Tails version are present in the filesystem 1.357
And all persistent directories from the old Tails version have safe access rights 2.229
After features/support/hooks.rb:335 1.068
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:58.868
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.144
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
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.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.022
And Tor is ready 12.697
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.890
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.703
Given I shutdown Tails and wait for the computer to power off 11.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.509
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.166
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.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.201
When the network is plugged 0.018
And Tor is ready 12.211
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.994
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.138
Given I shutdown Tails and wait for the computer to power off 8.437
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.647
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.130
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.020
And Tor is ready 10.863
Then the Upgrader considers the system as up-to-date 10.565
# 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.455
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.425
After features/support/hooks.rb:335 0.678
After features/support/hooks.rb:104 0.015
Tags: @product @automatic_upgrade
20.981
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 7.986
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.045
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.105
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.532
After features/support/hooks.rb:335 0.783
After features/support/hooks.rb:104 0.000