Project Number Date
test_Tails_ISO_test-snapshot-restore-improvements 10 24 Aug 2026, 12:04

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:41.790 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:21.441
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.546
When I start Tails from USB drive "old" with network unplugged 1:3.508
Then the boot device has safe access rights 2.635
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.154
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.852
After features/support/hooks.rb:108 0.018
Tags: @product
1:24.841
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login 50.356
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 23.893
And I take note of which tps features are available 7.119
Then a Tails persistence partition exists on USB drive "old" 0.535
And I shutdown Tails and wait for the computer to power off 2.606
After features/support/hooks.rb:339 0.458
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.134
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.056
Then Tails is running from USB drive "old" 0.218
And all tps features are active 7.180
When I write some files expected to persist 1.108
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.134
And all persistence configuration files have safe access rights 0.272
And all persistent directories from the old Tails version have safe access rights 2.097
And I take note of which tps features are available 6.212
And I shutdown Tails and wait for the computer to power off 4.058
# 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.692
After features/support/hooks.rb:339 0.215
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.192
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 5.765
And I log in to a new session 13.183
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.639
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.842
Then the running Tails is installed on USB drive "to_upgrade" 18.261
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 0.586
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.172
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.704
Then all tps features from the old Tails version are active 1.196
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.353
And the expected persistent files created with the old Tails version are present in the filesystem 1.003
And all persistent directories from the old Tails version have safe access rights 1.620
After features/support/hooks.rb:339 0.496
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:38.946
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.114
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.282
When the network is plugged 0.028
And Tor is ready 13.515
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.131
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.788
Given I shutdown Tails and wait for the computer to power off 5.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.869
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.283
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.218
When the network is plugged 0.027
And Tor is ready 10.285
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.865
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.503
Given I shutdown Tails and wait for the computer to power off 4.031
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.879
Then Tails is running version 6.3~testoverlayfs 0.041
And all tps features are active 9.638
And the file system changes introduced in version 6.3~testoverlayfs are present 0.317
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.151
When the network is plugged 0.027
And Tor is ready 10.363
Then the Upgrader considers the system as up-to-date 0.101
# 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.522
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:339 0.946
After features/support/hooks.rb:108 0.055
Tags: @product @automatic_upgrade
16.060
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.311
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.023
And the signing key used by the Upgrader is outdated 0.026
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.442
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.028
After features/support/hooks.rb:339 0.635
After features/support/hooks.rb:108 0.000