Project Number Date
test_Tails_ISO_stable 6371 12 May 2026, 13:27

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:47.582 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:5.476
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.275
When I start Tails from USB drive "old" with network unplugged 46.159
Then the boot device has safe access rights 3.139
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.276
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:335 1.447
After features/support/hooks.rb:104 0.008
Tags: @product
1:33.591
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 58.920
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 25.927
And I take note of which tps features are available 0.942
Then a Tails persistence partition exists on USB drive "old" 0.615
And I shutdown Tails and wait for the computer to power off 6.840
After features/support/hooks.rb:335 0.307
After features/support/hooks.rb:104 0.007
Tags: @product
1:32.196
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.725
Then Tails is running from USB drive "old" 0.274
And all tps features are active 1.180
When I write some files expected to persist 1.464
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.574
And all persistent directories from the old Tails version have safe access rights 2.175
And I take note of which tps features are available 0.200
And I shutdown Tails and wait for the computer to power off 8.432
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.893
After features/support/hooks.rb:335 0.166
After features/support/hooks.rb:104 0.007
Tags: @product
2:15.322
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 without a persistent partition and stopped at Tails Greeter's login screen 8.218
And I log in to a new session 13.986
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.990
And I plug USB drive "to_upgrade" 2.278
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.469
Then the running Tails is installed on USB drive "to_upgrade" 17.048
And I unplug USB drive "to_upgrade" 0.175
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:335 3.870
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.410
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.646
Then all tps features from the old Tails version are active 1.128
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.812
And the expected persistent files created with the old Tails version are present in the filesystem 1.254
And all persistent directories from the old Tails version have safe access rights 2.280
After features/support/hooks.rb:335 0.882
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
4:39.549
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.873
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.386
When the network is plugged 0.015
And Tor is ready 23.666
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.415
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.512
Given I shutdown Tails and wait for the computer to power off 19.117
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.344
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.159
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.260
When the network is plugged 0.053
And Tor is ready 22.139
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.452
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.938
Given I shutdown Tails and wait for the computer to power off 17.665
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.390
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.130
And the file system changes introduced in version 6.3~testoverlayfs are present 0.404
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.019
And Tor is ready 21.164
Then the Upgrader considers the system as up-to-date 0.118
# 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.369
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.412
After features/support/hooks.rb:335 1.090
After features/support/hooks.rb:104 0.024
Tags: @product @automatic_upgrade
27.034
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.914
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 18.261
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.442
After features/support/hooks.rb:335 0.799
After features/support/hooks.rb:104 0.000