Project Number Date
test_Tails_ISO_stable 6347 03 May 2026, 11:33

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 12:36.852 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.402
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.695
When I start Tails from USB drive "old" with network unplugged 46.348
Then the boot device has safe access rights 2.615
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 3.699
After features/support/hooks.rb:100 0.005
Tags: @product
1:23.060
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 50.480
Then Tails is running from USB drive "old" 0.214
And I create a persistent partition 23.201
And I take note of which tps features are available 0.652
Then a Tails persistence partition exists on USB drive "old" 0.551
And I shutdown Tails and wait for the computer to power off 7.913
After features/support/hooks.rb:331 0.272
After features/support/hooks.rb:100 0.007
Tags: @product
1:19.051
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.624
Then Tails is running from USB drive "old" 0.217
And all tps features are active 1.091
When I write some files expected to persist 1.210
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.474
And all persistent directories from the old Tails version have safe access rights 1.736
And I take note of which tps features are available 0.139
And I shutdown Tails and wait for the computer to power off 4.209
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.084
After features/support/hooks.rb:331 0.273
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.382
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.301
And I log in to a new session 16.871
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.854
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.559
Then the running Tails is installed on USB drive "to_upgrade" 16.309
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 3.984
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.044
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.478
Then all tps features from the old Tails version are active 0.970
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.580
And the expected persistent files created with the old Tails version are present in the filesystem 1.021
And all persistent directories from the old Tails version have safe access rights 1.732
After features/support/hooks.rb:331 0.754
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:50.596
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.554
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.239
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.015
And Tor is ready 26.806
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.357
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.468
Given I shutdown Tails and wait for the computer to power off 21.200
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.052
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.031
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.179
When the network is plugged 0.020
And Tor is ready 20.610
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.376
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.869
Given I shutdown Tails and wait for the computer to power off 17.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.286
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.046
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.013
And Tor is ready 20.981
Then the Upgrader considers the system as up-to-date 0.108
# 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.691
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:331 0.749
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
27.313
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.604
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 18.994
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.351
After features/support/hooks.rb:331 0.861
After features/support/hooks.rb:100 0.000