Project Number Date
test_Tails_ISO_stable 6695 27 Sep 2026, 12:17

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 17:43.958 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.269
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.898
When I start Tails from USB drive "old" with network unplugged 46.463
Then the boot device has safe access rights 2.115
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.051
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 1.775
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.365
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login 49.016
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 22.959
And I take note of which tps features are available 5.916
Then a Tails persistence partition exists on USB drive "old" 0.503
And I shutdown Tails and wait for the computer to power off 2.582
After features/support/hooks.rb:339 0.510
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.958
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 1.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.631
Then Tails is running from USB drive "old" 0.198
And all tps features are active 7.086
When I write some files expected to persist 1.077
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.204
And all persistent directories from the old Tails version have safe access rights 1.480
And I take note of which tps features are available 5.923
And I shutdown Tails and wait for the computer to power off 2.549
# 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.405
After features/support/hooks.rb:339 0.389
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.176
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.344
And I log in to a new session 11.211
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.778
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.075
Then the running Tails is installed on USB drive "to_upgrade" 17.279
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.909
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.398
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.329
Then all tps features from the old Tails version are active 1.101
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.188
And the expected persistent files created with the old Tails version are present in the filesystem 0.950
And all persistent directories from the old Tails version have safe access rights 1.514
After features/support/hooks.rb:339 0.786
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
7:42.821
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.049
And no SquashFS delta is installed 0.074
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.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.030
And Tor is ready 12.657
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4:3.221
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.572
Given I shutdown Tails and wait for the computer to power off 5.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.648
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.434
And the file system changes introduced in version 6.2~testoverlayfs are present 0.199
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.099
# 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.258
When the network is plugged 0.120
And Tor is ready 10.193
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.632
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.619
Given I shutdown Tails and wait for the computer to power off 5.433
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.292
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.603
And the file system changes introduced in version 6.3~testoverlayfs are present 0.276
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.110
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.036
And Tor is ready 10.837
Then the Upgrader considers the system as up-to-date 10.440
# 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.137
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.315
After features/support/hooks.rb:339 0.698
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
2:45.968
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 34.467
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.178
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 8.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:2.684
After features/support/hooks.rb:339 0.862
After features/support/hooks.rb:108 0.000