Project Number Date
test_Tails_ISO_stable 6507 15 Jul 2026, 11:36

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:42.456 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:12.483
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
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.966
When I start Tails from USB drive "old" with network unplugged 55.114
Then the boot device has safe access rights 2.698
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.415
After features/support/hooks.rb:108 0.007
Tags: @product
1:30.825
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 52.818
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 24.753
And I take note of which tps features are available 4.221
Then a Tails persistence partition exists on USB drive "old" 0.560
And I shutdown Tails and wait for the computer to power off 8.201
After features/support/hooks.rb:339 0.522
After features/support/hooks.rb:108 0.007
Tags: @product
1:30.108
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.992
Then Tails is running from USB drive "old" 0.267
And all tps features are active 4.587
When I write some files expected to persist 1.172
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.331
And all persistent directories from the old Tails version have safe access rights 1.921
And I take note of which tps features are available 3.736
And I shutdown Tails and wait for the computer to power off 4.184
# 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.622
After features/support/hooks.rb:339 0.253
After features/support/hooks.rb:108 0.005
Tags: @product
2:7.726
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 7.954
And I log in to a new session 11.362
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.853
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.759
Then the running Tails is installed on USB drive "to_upgrade" 14.328
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 1.902
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.651
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:3.662
Then all tps features from the old Tails version are active 0.971
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.481
And the expected persistent files created with the old Tails version are present in the filesystem 1.182
And all persistent directories from the old Tails version have safe access rights 2.046
After features/support/hooks.rb:339 0.532
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:50.896
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 8.033
And no SquashFS delta is installed 0.065
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.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.015
And Tor is ready 12.890
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.228
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.039
Given I shutdown Tails and wait for the computer to power off 9.482
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.353
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 4.562
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.178
When the network is plugged 0.014
And Tor is ready 9.910
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.067
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.176
Given I shutdown Tails and wait for the computer to power off 7.831
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.076
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.925
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.014
And Tor is ready 9.960
Then the Upgrader considers the system as up-to-date 10.587
# 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.083
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:339 0.948
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.762
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.391
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 9.700
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.277
After features/support/hooks.rb:339 1.017
After features/support/hooks.rb:108 0.000