Project Number Date
test_Tails_ISO_devel 4419 27 May 2026, 19:27

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:28.486 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:4.523
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.873
When I start Tails from USB drive "old" with network unplugged 45.981
Then the boot device has safe access rights 2.762
And Tails is running from USB drive "old" 0.275
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:335 3.607
After features/support/hooks.rb:104 0.006
Tags: @product
1:30.440
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 54.254
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 26.469
And I take note of which tps features are available 0.378
Then a Tails persistence partition exists on USB drive "old" 0.597
And I shutdown Tails and wait for the computer to power off 8.401
After features/support/hooks.rb:335 0.423
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.655
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.286
Then Tails is running from USB drive "old" 0.229
And all tps features are active 1.145
When I write some files expected to persist 1.451
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 1.738
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 8.064
# 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" 12.039
After features/support/hooks.rb:335 0.213
After features/support/hooks.rb:104 0.012
Tags: @product
2:11.809
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.763
And I log in to a new session 12.450
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.813
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.258
Then the running Tails is installed on USB drive "to_upgrade" 16.032
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:335 2.309
After features/support/hooks.rb:104 0.000
Tags: @product
1:9.582
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.502
Then all tps features from the old Tails version are active 0.954
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.514
And the expected persistent files created with the old Tails version are present in the filesystem 1.121
And all persistent directories from the old Tails version have safe access rights 2.163
After features/support/hooks.rb:335 0.672
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:43.380
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.050
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.015
And Tor is ready 12.713
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.414
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.254
Given I shutdown Tails and wait for the computer to power off 9.582
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.109
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.185
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.169
# 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.190
When the network is plugged 0.018
And Tor is ready 10.834
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.713
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.435
Given I shutdown Tails and wait for the computer to power off 7.909
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.675
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.494
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.015
And Tor is ready 10.228
Then the Upgrader considers the system as up-to-date 10.632
# 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.324
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.392
After features/support/hooks.rb:335 0.642
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
21.094
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.447
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.928
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.403
After features/support/hooks.rb:335 0.694
After features/support/hooks.rb:104 0.000