Project Number Date
test_Tails_ISO_stable 6396 21 May 2026, 11:53

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:9.077 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:13.779
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.144
When I start Tails from USB drive "old" with network unplugged 54.723
Then the boot device has safe access rights 3.101
And Tails is running from USB drive "old" 0.262
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:335 1.502
After features/support/hooks.rb:104 0.008
Tags: @product
1:30.400
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 "old" with network unplugged and I login 57.873
Then Tails is running from USB drive "old" 0.274
And I create a persistent partition 26.020
And I take note of which tps features are available 0.383
Then a Tails persistence partition exists on USB drive "old" 0.640
And I shutdown Tails and wait for the computer to power off 5.132
After features/support/hooks.rb:335 0.509
After features/support/hooks.rb:104 0.008
Tags: @product
1:31.456
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.400
Then Tails is running from USB drive "old" 0.330
And all tps features are active 1.268
When I write some files expected to persist 1.271
# 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.316
And all persistent directories from the old Tails version have safe access rights 1.960
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 8.442
# 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.064
After features/support/hooks.rb:335 0.450
After features/support/hooks.rb:104 0.007
Tags: @product
2:16.438
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 without a persistent partition and stopped at Tails Greeter's login screen 8.722
And I log in to a new session 14.724
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.270
And I plug USB drive "to_upgrade" 2.443
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.372
Then the running Tails is installed on USB drive "to_upgrade" 16.610
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:335 2.074
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.506
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.245
Then all tps features from the old Tails version are active 1.279
And Tails is running from USB drive "to_upgrade" 0.240
And the boot device has safe access rights 2.950
And the expected persistent files created with the old Tails version are present in the filesystem 1.402
And all persistent directories from the old Tails version have safe access rights 2.314
After features/support/hooks.rb:335 0.845
After features/support/hooks.rb:104 0.045
Tags: @product @automatic_upgrade
3:58.812
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 8.146
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.049
And Tor is ready 13.179
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.455
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.034
Given I shutdown Tails and wait for the computer to power off 9.954
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.736
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.525
And the file system changes introduced in version 6.2~testoverlayfs are present 0.253
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.180
# 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.386
When the network is plugged 0.014
And Tor is ready 9.976
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.988
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.465
Given I shutdown Tails and wait for the computer to power off 7.362
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.475
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.439
And the file system changes introduced in version 6.3~testoverlayfs are present 0.595
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.015
And Tor is ready 11.365
Then the Upgrader considers the system as up-to-date 10.635
# 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 5.570
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.511
After features/support/hooks.rb:335 0.820
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
22.684
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 7.908
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 11.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.637
After features/support/hooks.rb:335 0.553
After features/support/hooks.rb:104 0.000