Project Number Date
test_Tails_ISO_stable 6718 02 Oct 2026, 11:32

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:3.175 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
58.287
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.598
When I start Tails from USB drive "old" with network unplugged 40.573
Then the boot device has safe access rights 2.382
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.167
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.782
After features/support/hooks.rb:108 0.016
Tags: @product
1:22.554
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 "old" with network unplugged and I login 48.092
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 23.261
And I take note of which tps features are available 6.559
Then a Tails persistence partition exists on USB drive "old" 0.474
And I shutdown Tails and wait for the computer to power off 3.828
After features/support/hooks.rb:339 0.281
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.225
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:0.566
Then Tails is running from USB drive "old" 0.207
And all tps features are active 7.673
When I write some files expected to persist 1.089
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.233
And all persistent directories from the old Tails version have safe access rights 1.705
And I take note of which tps features are available 5.973
And I shutdown Tails and wait for the computer to power off 2.577
# 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.956
After features/support/hooks.rb:339 0.582
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.036
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 without a persistent partition and stopped at Tails Greeter's login screen 8.240
And I log in to a new session 12.681
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.602
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.619
Then the running Tails is installed on USB drive "to_upgrade" 18.345
And I unplug USB drive "to_upgrade" 0.178
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 1.821
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.952
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.118
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.692
Then all tps features from the old Tails version are active 1.146
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 2.462
And the expected persistent files created with the old Tails version are present in the filesystem 0.938
And all persistent directories from the old Tails version have safe access rights 1.380
After features/support/hooks.rb:339 0.670
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:29.840
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 8.081
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
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.154
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.313
When the network is plugged 0.031
And Tor is ready 12.708
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.331
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.337
Given I shutdown Tails and wait for the computer to power off 5.519
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.916
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.439
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.178
When the network is plugged 0.037
And Tor is ready 10.478
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.920
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.066
Given I shutdown Tails and wait for the computer to power off 2.548
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.524
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.153
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.175
When the network is plugged 0.032
And Tor is ready 11.286
Then the Upgrader considers the system as up-to-date 0.091
# 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.821
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.326
After features/support/hooks.rb:339 1.031
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
19.279
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 8.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.929
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.941
After features/support/hooks.rb:339 0.854
After features/support/hooks.rb:108 0.000