Project Number Date
test_Tails_ISO_test-snapshot-restore-improvements 5 23 Aug 2026, 13:08

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:53.037 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:23.528
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.106
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.935
When I start Tails from USB drive "old" with network unplugged 1:5.479
Then the boot device has safe access rights 2.365
And Tails is running from USB drive "old" 0.195
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:339 1.346
After features/support/hooks.rb:108 0.013
Tags: @product
1:27.803
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.145
And I start Tails from USB drive "old" with network unplugged and I login 50.244
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 25.104
And I take note of which tps features are available 7.168
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 4.127
After features/support/hooks.rb:339 0.581
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.004
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.511
Then Tails is running from USB drive "old" 0.222
And all tps features are active 8.123
When I write some files expected to persist 1.138
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.293
And all persistent directories from the old Tails version have safe access rights 2.056
And I take note of which tps features are available 6.600
And I shutdown Tails and wait for the computer to power off 3.848
# 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.958
After features/support/hooks.rb:339 0.418
After features/support/hooks.rb:108 0.020
Tags: @product
2:11.670
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 5.755
And I log in to a new session 12.699
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.690
And I plug USB drive "to_upgrade" 2.247
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.506
Then the running Tails is installed on USB drive "to_upgrade" 18.485
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 2.154
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.384
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.846
Then all tps features from the old Tails version are active 1.208
And Tails is running from USB drive "to_upgrade" 0.177
And the boot device has safe access rights 2.342
And the expected persistent files created with the old Tails version are present in the filesystem 0.901
And all persistent directories from the old Tails version have safe access rights 1.816
After features/support/hooks.rb:339 0.841
After features/support/hooks.rb:108 0.007
3:41.927
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.600
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.277
When the network is plugged 0.032
And Tor is ready 12.080
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.365
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.180
Given I shutdown Tails and wait for the computer to power off 5.454
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.755
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.349
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.217
When the network is plugged 0.027
And Tor is ready 11.515
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.312
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.275
Given I shutdown Tails and wait for the computer to power off 2.726
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.793
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.456
And the file system changes introduced in version 6.3~testoverlayfs are present 0.433
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.073
And Tor is ready 11.472
Then the Upgrader considers the system as up-to-date 0.094
# 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.580
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.367
After features/support/hooks.rb:339 0.928
After features/support/hooks.rb:108 0.010
16.718
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.600
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 9.707
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.005
After features/support/hooks.rb:339 0.968
After features/support/hooks.rb:108 0.000