Project Number Date
test_Tails_ISO_devel 4479 01 Jul 2026, 15:51

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:13.824 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.429
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.817
When I start Tails from USB drive "old" with network unplugged 46.872
Then the boot device has safe access rights 2.915
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.177
After features/support/hooks.rb:108 0.007
Tags: @product
1:35.619
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 57.083
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 25.640
And I take note of which tps features are available 4.505
Then a Tails persistence partition exists on USB drive "old" 0.605
And I shutdown Tails and wait for the computer to power off 7.483
After features/support/hooks.rb:339 0.307
After features/support/hooks.rb:108 0.006
Tags: @product
1:43.401
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.963
Then Tails is running from USB drive "old" 0.244
And all tps features are active 5.623
When I write some files expected to persist 1.538
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 2.259
And I take note of which tps features are available 4.752
And I shutdown Tails and wait for the computer to power off 8.328
# 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.983
After features/support/hooks.rb:339 0.487
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.305
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 without a persistent partition and stopped at Tails Greeter's login screen 8.052
And I log in to a new session 12.367
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.814
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.453
Then the running Tails is installed on USB drive "to_upgrade" 16.149
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 2.172
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.948
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.690
Then all tps features from the old Tails version are active 1.016
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.497
And the expected persistent files created with the old Tails version are present in the filesystem 1.273
And all persistent directories from the old Tails version have safe access rights 2.179
After features/support/hooks.rb:339 0.779
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:3.130
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.858
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.347
When the network is plugged 0.017
And Tor is ready 13.911
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.016
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.002
Given I shutdown Tails and wait for the computer to power off 8.455
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.223
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 4.909
And the file system changes introduced in version 6.2~testoverlayfs are present 0.212
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.172
# 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.207
When the network is plugged 0.016
And Tor is ready 10.232
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.503
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.839
Given I shutdown Tails and wait for the computer to power off 8.137
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.331
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.735
And the file system changes introduced in version 6.3~testoverlayfs are present 0.370
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.294
When the network is plugged 0.016
And Tor is ready 11.571
Then the Upgrader considers the system as up-to-date 10.581
# 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.844
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.464
After features/support/hooks.rb:339 0.943
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
19.990
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 7.779
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.959
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.919
After features/support/hooks.rb:339 0.735
After features/support/hooks.rb:108 0.000