Project Number Date
test_Tails_ISO_stable 6114 03 Feb 2026, 08:09

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 13:4.672 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:53.472
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.311
When I start Tails from USB drive "old" with network unplugged 1:35.780
Then the boot device has safe access rights 2.595
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 1.406
After features/support/hooks.rb:100 0.026
Tags: @product
1:24.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 55.172
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 23.640
And I take note of which tps features are available 0.623
Then a Tails persistence partition exists on USB drive "old" 0.616
And I shutdown Tails and wait for the computer to power off 4.056
After features/support/hooks.rb:331 0.501
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.634
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.657
Then Tails is running from USB drive "old" 0.213
And all tps features are active 1.050
When I write some files expected to persist 1.257
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.290
And all persistent directories from the old Tails version have safe access rights 1.851
And I take note of which tps features are available 0.132
And I shutdown Tails and wait for the computer to power off 7.857
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.108
After features/support/hooks.rb:331 0.279
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.076
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.524
And I log in to a new session 13.121
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.689
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:52.652
Then the running Tails is installed on USB drive "to_upgrade" 15.357
And I unplug USB drive "to_upgrade" 0.174
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 3.710
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.420
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.143
Then all tps features from the old Tails version are active 0.781
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.444
And the expected persistent files created with the old Tails version are present in the filesystem 0.999
And all persistent directories from the old Tails version have safe access rights 1.780
After features/support/hooks.rb:331 0.785
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
3:53.975
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.821
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.478
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.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.016
And Tor is ready 13.916
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.129
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.189
Given I shutdown Tails and wait for the computer to power off 26.408
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.159
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.048
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
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.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.198
When the network is plugged 0.019
And Tor is ready 9.836
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.046
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.500
Given I shutdown Tails and wait for the computer to power off 8.168
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.886
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.126
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.013
And Tor is ready 9.588
Then the Upgrader considers the system as up-to-date 10.472
# 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.712
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.375
After features/support/hooks.rb:331 1.010
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
48.681
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.443
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 40.513
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.362
After features/support/hooks.rb:331 0.503
After features/support/hooks.rb:100 0.000