Project Number Date
test_Tails_ISO_stable 6214 18 Mar 2026, 07:13

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:14.283 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:46.437
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.522
When I start Tails from USB drive "old" with network unplugged 1:28.476
Then the boot device has safe access rights 2.687
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.060
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.780
After features/support/hooks.rb:100 0.023
Tags: @product
1:28.938
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 55.821
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 23.709
And I take note of which tps features are available 0.656
Then a Tails persistence partition exists on USB drive "old" 0.513
And I shutdown Tails and wait for the computer to power off 7.910
After features/support/hooks.rb:331 0.394
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.842
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 "old" with network unplugged and I login with persistence enabled 59.483
Then Tails is running from USB drive "old" 0.260
And all tps features are active 1.058
When I write some files expected to persist 1.225
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 1.848
And I take note of which tps features are available 0.156
And I shutdown Tails and wait for the computer to power off 7.924
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.215
After features/support/hooks.rb:331 0.441
After features/support/hooks.rb:100 0.006
Tags: @product
2:23.282
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 without a persistent partition and stopped at Tails Greeter's login screen 10.169
And I log in to a new session 16.313
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.857
And I plug USB drive "to_upgrade" 2.279
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.683
Then the running Tails is installed on USB drive "to_upgrade" 15.527
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.235
After features/support/hooks.rb:331 4.112
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.919
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.205
Then all tps features from the old Tails version are active 0.924
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.496
And the expected persistent files created with the old Tails version are present in the filesystem 1.087
And all persistent directories from the old Tails version have safe access rights 1.914
After features/support/hooks.rb:331 0.878
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
4:34.221
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.394
And no SquashFS delta is installed 0.166
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.195
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.354
When the network is plugged 0.022
And Tor is ready 22.616
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.390
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.391
Given I shutdown Tails and wait for the computer to power off 20.768
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.892
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.135
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.228
When the network is plugged 0.015
And Tor is ready 20.294
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.415
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.634
Given I shutdown Tails and wait for the computer to power off 17.059
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.472
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.191
And the file system changes introduced in version 6.3~testoverlayfs are present 0.411
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.212
When the network is plugged 0.024
And Tor is ready 20.796
Then the Upgrader considers the system as up-to-date 0.093
# 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.670
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.375
After features/support/hooks.rb:331 0.947
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
27.641
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 7.682
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 19.136
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.394
After features/support/hooks.rb:331 0.757
After features/support/hooks.rb:100 0.000