Project Number Date
test_Tails_ISO_stable 6400 23 May 2026, 11:19

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 11:8.710 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:4.455
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 12.883
When I start Tails from USB drive "old" with network unplugged 47.031
Then the boot device has safe access rights 2.767
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:335 3.688
After features/support/hooks.rb:104 0.043
Tags: @product
1:24.314
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 53.090
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 23.542
And I take note of which tps features are available 0.313
Then a Tails persistence partition exists on USB drive "old" 0.511
And I shutdown Tails and wait for the computer to power off 6.566
After features/support/hooks.rb:335 0.536
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.536
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.689
Then Tails is running from USB drive "old" 0.219
And all tps features are active 1.280
When I write some files expected to persist 1.229
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
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.725
And I take note of which tps features are available 0.175
And I shutdown Tails and wait for the computer to power off 7.913
# 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" 11.734
After features/support/hooks.rb:335 0.291
After features/support/hooks.rb:104 0.006
Tags: @product
2:10.678
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.068
And I log in to a new session 13.230
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.789
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.387
Then the running Tails is installed on USB drive "to_upgrade" 14.687
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:335 2.279
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.191
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.035
Then all tps features from the old Tails version are active 0.977
And Tails is running from USB drive "to_upgrade" 0.260
And the boot device has safe access rights 2.819
And the expected persistent files created with the old Tails version are present in the filesystem 1.132
And all persistent directories from the old Tails version have safe access rights 1.918
After features/support/hooks.rb:335 0.598
After features/support/hooks.rb:104 0.006
3:34.523
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.980
And no SquashFS delta is installed 0.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
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.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.370
When the network is plugged 0.015
And Tor is ready 12.328
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.178
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.337
Given I shutdown Tails and wait for the computer to power off 9.437
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.573
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.129
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.205
When the network is plugged 0.013
And Tor is ready 9.694
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.227
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.241
Given I shutdown Tails and wait for the computer to power off 7.918
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.141
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.056
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.013
And Tor is ready 10.676
Then the Upgrader considers the system as up-to-date 10.504
# 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.344
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.441
After features/support/hooks.rb:335 0.871
After features/support/hooks.rb:104 0.011
21.010
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.451
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.896
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.310
After features/support/hooks.rb:335 0.769
After features/support/hooks.rb:104 0.000