Project Number Date
test_Tails_ISO_test-snapshot-restore-improvements 12 24 Aug 2026, 13:34

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:47.569 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:6.321
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 15.039
When I start Tails from USB drive "old" with network unplugged 47.305
Then the boot device has safe access rights 2.199
And Tails is running from USB drive "old" 0.208
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 3.742
After features/support/hooks.rb:108 0.022
Tags: @product
1:32.997
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 52.127
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 26.195
And I take note of which tps features are available 9.580
Then a Tails persistence partition exists on USB drive "old" 0.601
And I shutdown Tails and wait for the computer to power off 4.155
After features/support/hooks.rb:339 0.389
After features/support/hooks.rb:108 0.006
Tags: @product
1:45.376
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.876
Then Tails is running from USB drive "old" 0.330
And all tps features are active 10.115
When I write some files expected to persist 1.344
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 2.079
And I take note of which tps features are available 6.574
And I shutdown Tails and wait for the computer to power off 2.697
# 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.751
After features/support/hooks.rb:339 0.432
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.324
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 6.180
And I log in to a new session 14.282
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.748
And I plug USB drive "to_upgrade" 2.342
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.100
Then the running Tails is installed on USB drive "to_upgrade" 19.450
And I unplug USB drive "to_upgrade" 0.101
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.873
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.478
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.245
Then all tps features from the old Tails version are active 1.360
And Tails is running from USB drive "to_upgrade" 0.424
And the boot device has safe access rights 2.984
And the expected persistent files created with the old Tails version are present in the filesystem 1.187
And all persistent directories from the old Tails version have safe access rights 2.191
After features/support/hooks.rb:339 0.737
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:39.065
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 5.683
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.162
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.306
When the network is plugged 0.034
And Tor is ready 14.032
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.007
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.192
Given I shutdown Tails and wait for the computer to power off 5.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.560
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.159
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# 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.231
When the network is plugged 0.025
And Tor is ready 9.854
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.716
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.861
Given I shutdown Tails and wait for the computer to power off 3.879
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.702
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.702
And the file system changes introduced in version 6.3~testoverlayfs are present 0.293
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.028
And Tor is ready 10.906
Then the Upgrader considers the system as up-to-date 0.137
# 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.741
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.396
After features/support/hooks.rb:339 0.853
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
17.005
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 5.321
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
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.026
And Tor is ready 8.974
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.340
After features/support/hooks.rb:339 0.721
After features/support/hooks.rb:108 0.000