Project Number Date
test_Tails_ISO_stable 6631 03 Sep 2026, 07:30

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:46.433 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:9.105
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.210
When I start Tails from USB drive "old" with network unplugged 50.431
Then the boot device has safe access rights 2.654
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.174
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 1.300
After features/support/hooks.rb:108 0.017
Tags: @product
1:31.038
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login 53.021
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 25.742
And I take note of which tps features are available 7.279
Then a Tails persistence partition exists on USB drive "old" 0.496
And I shutdown Tails and wait for the computer to power off 4.121
After features/support/hooks.rb:339 0.373
After features/support/hooks.rb:108 0.016
Tags: @product
1:37.117
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.999
Then Tails is running from USB drive "old" 0.347
And all tps features are active 8.010
When I write some files expected to persist 1.319
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.271
And all persistent directories from the old Tails version have safe access rights 1.555
And I take note of which tps features are available 6.204
And I shutdown Tails and wait for the computer to power off 3.873
# 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.305
After features/support/hooks.rb:339 0.221
After features/support/hooks.rb:108 0.005
Tags: @product
2:18.542
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 9.443
And I log in to a new session 13.485
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.766
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.443
Then the running Tails is installed on USB drive "to_upgrade" 19.962
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.110
After features/support/hooks.rb:339 1.645
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.280
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.992
Then all tps features from the old Tails version are active 1.264
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.772
And the expected persistent files created with the old Tails version are present in the filesystem 1.047
And all persistent directories from the old Tails version have safe access rights 1.886
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:39.289
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.377
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.157
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.024
And Tor is ready 13.540
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.379
Given I shutdown Tails and wait for the computer to power off 5.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.198
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 7.629
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
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.155
# 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.192
When the network is plugged 0.033
And Tor is ready 11.033
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.952
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.737
Given I shutdown Tails and wait for the computer to power off 4.101
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.358
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 10.202
And the file system changes introduced in version 6.3~testoverlayfs are present 0.308
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.098
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.025
And Tor is ready 10.599
Then the Upgrader considers the system as up-to-date 0.112
# 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.496
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:339 0.635
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.060
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.358
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 10.469
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.901
After features/support/hooks.rb:339 0.659
After features/support/hooks.rb:108 0.000