Project Number Date
test_Tails_ISO_stable 6156 19 Feb 2026, 12:02

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 14:12.745 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:38.474
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.882
When I start Tails from USB drive "old" with network unplugged 1:19.012
Then the boot device has safe access rights 2.759
And Tails is running from USB drive "old" 0.258
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 1.813
After features/support/hooks.rb:100 0.015
Tags: @product
1:29.949
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 57.292
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 26.501
And I take note of which tps features are available 0.864
Then a Tails persistence partition exists on USB drive "old" 0.613
And I shutdown Tails and wait for the computer to power off 4.277
After features/support/hooks.rb:331 0.535
After features/support/hooks.rb:100 0.008
Tags: @product
1:30.176
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.381
Then Tails is running from USB drive "old" 0.270
And all tps features are active 1.207
When I write some files expected to persist 1.340
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 1.889
And I take note of which tps features are available 0.181
And I shutdown Tails and wait for the computer to power off 8.651
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.669
After features/support/hooks.rb:331 0.202
After features/support/hooks.rb:100 0.012
Tags: @product
2:23.159
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.291
And I log in to a new session 14.407
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.920
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.448
Then the running Tails is installed on USB drive "to_upgrade" 17.544
And I unplug USB drive "to_upgrade" 0.166
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 0.805
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.082
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.870
Then all tps features from the old Tails version are active 1.077
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.707
And the expected persistent files created with the old Tails version are present in the filesystem 1.175
And all persistent directories from the old Tails version have safe access rights 1.909
After features/support/hooks.rb:331 0.650
After features/support/hooks.rb:100 0.007
5:30.943
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 9.063
And no SquashFS delta is installed 0.218
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
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.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.026
And Tor is ready 45.813
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.529
Given I shutdown Tails and wait for the computer to power off 22.539
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.895
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.390
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
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.145
# 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.290
When the network is plugged 0.030
And Tor is ready 21.959
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.593
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.680
Given I shutdown Tails and wait for the computer to power off 13.635
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.473
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.251
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
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.170
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 41.679
Then the Upgrader considers the system as up-to-date 0.126
# 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 5.567
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:331 0.865
After features/support/hooks.rb:100 0.020
27.959
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.544
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 18.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.366
After features/support/hooks.rb:331 0.796
After features/support/hooks.rb:100 0.000