Project Number Date
test_Tails_ISO_stable 6207 16 Mar 2026, 12:48

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 14:1.960 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:34.696
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.986
When I start Tails from USB drive "old" with network unplugged 1:14.774
Then the boot device has safe access rights 3.073
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:331 1.594
After features/support/hooks.rb:100 0.043
Tags: @product
1:34.441
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 59.455
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 25.980
And I take note of which tps features are available 0.782
Then a Tails persistence partition exists on USB drive "old" 0.619
And I shutdown Tails and wait for the computer to power off 7.212
After features/support/hooks.rb:331 0.420
After features/support/hooks.rb:100 0.007
Tags: @product
1:34.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.966
Then Tails is running from USB drive "old" 0.263
And all tps features are active 1.114
When I write some files expected to persist 1.236
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.151
And I take note of which tps features are available 0.221
And I shutdown Tails and wait for the computer to power off 8.477
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.998
After features/support/hooks.rb:331 0.261
After features/support/hooks.rb:100 0.006
Tags: @product
2:26.895
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.283
And I log in to a new session 13.385
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.056
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.101
Then the running Tails is installed on USB drive "to_upgrade" 20.398
And I unplug USB drive "to_upgrade" 0.180
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:331 3.875
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.735
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.898
Then all tps features from the old Tails version are active 1.026
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 3.051
And the expected persistent files created with the old Tails version are present in the filesystem 1.343
And all persistent directories from the old Tails version have safe access rights 2.057
After features/support/hooks.rb:331 0.544
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
5:7.969
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.160
And no SquashFS delta is installed 0.099
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.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.407
When the network is plugged 0.016
And Tor is ready 27.752
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.418
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.817
Given I shutdown Tails and wait for the computer to power off 20.673
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.415
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.281
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.233
When the network is plugged 0.018
And Tor is ready 23.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.394
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.689
Given I shutdown Tails and wait for the computer to power off 12.307
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.555
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.282
And the file system changes introduced in version 6.3~testoverlayfs are present 0.408
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.022
And Tor is ready 39.627
Then the Upgrader considers the system as up-to-date 0.138
# 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.400
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.345
After features/support/hooks.rb:331 1.122
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
27.115
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.747
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.052
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 18.561
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.462
After features/support/hooks.rb:331 0.682
After features/support/hooks.rb:100 0.000