Project Number Date
test_Tails_ISO_devel 4466 23 Jun 2026, 11:16

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:28.136 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
58.682
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.962
When I start Tails from USB drive "old" with network unplugged 41.404
Then the boot device has safe access rights 2.455
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.245
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:339 1.267
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.594
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 52.631
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 24.078
And I take note of which tps features are available 4.289
Then a Tails persistence partition exists on USB drive "old" 0.529
And I shutdown Tails and wait for the computer to power off 2.743
After features/support/hooks.rb:339 0.280
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.591
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.908
Then Tails is running from USB drive "old" 0.240
And all tps features are active 4.645
When I write some files expected to persist 1.277
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.338
And all persistent directories from the old Tails version have safe access rights 1.848
And I take note of which tps features are available 4.005
And I shutdown Tails and wait for the computer to power off 8.290
# 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.790
After features/support/hooks.rb:339 0.238
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.891
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.132
And I log in to a new session 11.496
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.050
Then the running Tails is installed on USB drive "to_upgrade" 14.962
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.902
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.292
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.044
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.159
Then all tps features from the old Tails version are active 0.953
And Tails is running from USB drive "to_upgrade" 0.262
And the boot device has safe access rights 2.745
And the expected persistent files created with the old Tails version are present in the filesystem 1.219
And all persistent directories from the old Tails version have safe access rights 1.906
After features/support/hooks.rb:339 0.953
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:48.781
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.151
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.417
When the network is plugged 0.020
And Tor is ready 13.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.826
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.419
Given I shutdown Tails and wait for the computer to power off 9.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.232
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 4.623
And the file system changes introduced in version 6.2~testoverlayfs are present 0.195
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.229
When the network is plugged 0.023
And Tor is ready 9.799
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.253
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.103
Given I shutdown Tails and wait for the computer to power off 8.222
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.474
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 4.800
And the file system changes introduced in version 6.3~testoverlayfs are present 0.350
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.186
When the network is plugged 0.013
And Tor is ready 11.132
Then the Upgrader considers the system as up-to-date 10.499
# 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.838
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.311
After features/support/hooks.rb:339 0.716
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.301
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.431
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 8.476
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.050
After features/support/hooks.rb:339 0.907
After features/support/hooks.rb:108 0.000