Project Number Date
test_Tails_ISO_stable 6644 08 Sep 2026, 00:09

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 10:38.412 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
55.225
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.020
When I start Tails from USB drive "old" with network unplugged 38.483
Then the boot device has safe access rights 1.936
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.826
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.129
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 45.990
Then Tails is running from USB drive "old" 0.211
And I create a persistent partition 23.197
And I take note of which tps features are available 6.178
Then a Tails persistence partition exists on USB drive "old" 0.456
And I shutdown Tails and wait for the computer to power off 4.021
After features/support/hooks.rb:339 0.170
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.904
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.723
Then Tails is running from USB drive "old" 0.214
And all tps features are active 6.731
When I write some files expected to persist 0.985
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.226
And all persistent directories from the old Tails version have safe access rights 1.496
And I take note of which tps features are available 6.077
And I shutdown Tails and wait for the computer to power off 5.055
# 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.148
After features/support/hooks.rb:339 0.437
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.723
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 8.440
And I log in to a new session 10.071
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.716
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.156
Then the running Tails is installed on USB drive "to_upgrade" 17.892
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 1.660
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.153
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.012
Then all tps features from the old Tails version are active 0.975
And Tails is running from USB drive "to_upgrade" 0.177
And the boot device has safe access rights 1.731
And the expected persistent files created with the old Tails version are present in the filesystem 0.814
And all persistent directories from the old Tails version have safe access rights 1.367
After features/support/hooks.rb:339 0.474
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:20.136
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.007
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.235
When the network is plugged 0.033
And Tor is ready 12.380
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.880
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.393
Given I shutdown Tails and wait for the computer to power off 5.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.183
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.137
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
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.109
# 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.151
When the network is plugged 0.034
And Tor is ready 10.069
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.477
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.373
Given I shutdown Tails and wait for the computer to power off 2.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.777
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.608
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.047
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.023
And Tor is ready 9.982
Then the Upgrader considers the system as up-to-date 0.104
# 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.406
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.312
After features/support/hooks.rb:339 0.711
After features/support/hooks.rb:108 0.036
Tags: @product @automatic_upgrade
19.140
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.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
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.036
And Tor is ready 8.103
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.601
After features/support/hooks.rb:339 0.514
After features/support/hooks.rb:108 0.000