Project Number Date
test_Tails_ISO_stable 6259 03 Apr 2026, 07:24

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 13:38.084 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:48.723
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.118
When I start Tails from USB drive "old" with network unplugged 1:29.907
Then the boot device has safe access rights 2.917
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 3.603
After features/support/hooks.rb:100 0.051
Tags: @product
1:32.341
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 1:0.049
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 22.895
And I take note of which tps features are available 0.702
Then a Tails persistence partition exists on USB drive "old" 0.478
And I shutdown Tails and wait for the computer to power off 7.900
After features/support/hooks.rb:331 0.644
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.924
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.590
Then Tails is running from USB drive "old" 0.324
And all tps features are active 1.129
When I write some files expected to persist 1.282
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 1.838
And I take note of which tps features are available 0.137
And I shutdown Tails and wait for the computer to power off 7.793
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.174
After features/support/hooks.rb:331 0.429
After features/support/hooks.rb:100 0.006
Tags: @product
2:28.935
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.983
And I log in to a new session 25.170
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.963
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.336
Then the running Tails is installed on USB drive "to_upgrade" 15.981
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 3.888
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.964
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.105
Then all tps features from the old Tails version are active 1.056
And Tails is running from USB drive "to_upgrade" 0.281
And the boot device has safe access rights 2.511
And the expected persistent files created with the old Tails version are present in the filesystem 1.033
And all persistent directories from the old Tails version have safe access rights 1.921
After features/support/hooks.rb:331 0.718
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:45.979
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.858
And no SquashFS delta is installed 0.233
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.015
And Tor is ready 23.352
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.342
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.787
Given I shutdown Tails and wait for the computer to power off 28.988
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.719
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.161
And the file system changes introduced in version 6.2~testoverlayfs are present 0.189
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.204
When the network is plugged 0.014
And Tor is ready 21.161
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.349
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.743
Given I shutdown Tails and wait for the computer to power off 18.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.014
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.025
And the file system changes introduced in version 6.3~testoverlayfs are present 0.420
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.015
And Tor is ready 20.783
Then the Upgrader considers the system as up-to-date 0.117
# 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.202
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.369
After features/support/hooks.rb:331 1.004
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
28.214
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.635
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 19.789
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.394
After features/support/hooks.rb:331 1.061
After features/support/hooks.rb:100 0.000