Project Number Date
test_Tails_ISO_test-snapshot-restore-improvements 4 21 Aug 2026, 22:02

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:26.475 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:20.564
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.064
When I start Tails from USB drive "old" with network unplugged 1:3.694
Then the boot device has safe access rights 2.073
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 1.163
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.143
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 48.612
Then Tails is running from USB drive "old" 0.201
And I create a persistent partition 24.030
And I take note of which tps features are available 7.114
Then a Tails persistence partition exists on USB drive "old" 0.511
And I shutdown Tails and wait for the computer to power off 2.581
After features/support/hooks.rb:339 0.219
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.069
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.310
Then Tails is running from USB drive "old" 0.375
And all tps features are active 6.959
When I write some files expected to persist 1.322
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.135
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 1.695
And I take note of which tps features are available 6.083
And I shutdown Tails and wait for the computer to power off 2.604
# 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.187
After features/support/hooks.rb:339 0.211
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.964
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.324
And I log in to a new session 11.136
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.720
And I plug USB drive "to_upgrade" 2.360
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.147
Then the running Tails is installed on USB drive "to_upgrade" 19.024
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 3.611
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.415
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.869
Then all tps features from the old Tails version are active 1.273
And Tails is running from USB drive "to_upgrade" 0.267
And the boot device has safe access rights 2.275
And the expected persistent files created with the old Tails version are present in the filesystem 0.951
And all persistent directories from the old Tails version have safe access rights 1.678
After features/support/hooks.rb:339 0.787
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
3:33.382
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 with a persistent partition enabled and logged in 5.314
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
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.248
When the network is plugged 0.030
And Tor is ready 13.261
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.971
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.492
Given I shutdown Tails and wait for the computer to power off 5.213
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.204
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.442
And the file system changes introduced in version 6.2~testoverlayfs are present 0.181
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# 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.195
When the network is plugged 0.038
And Tor is ready 10.104
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.425
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.932
Given I shutdown Tails and wait for the computer to power off 3.904
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.334
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.902
And the file system changes introduced in version 6.3~testoverlayfs are present 0.361
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.027
And Tor is ready 9.730
Then the Upgrader considers the system as up-to-date 10.451
# 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.109
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.412
After features/support/hooks.rb:339 1.136
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
17.935
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.790
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.036
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 9.762
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.011
After features/support/hooks.rb:339 0.803
After features/support/hooks.rb:108 0.000