Project Number Date
test_Tails_ISO_devel 4242 19 Feb 2026, 12:05

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:36.603 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:21.045
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.723
When I start Tails from USB drive "old" with network unplugged 1:1.491
Then the boot device has safe access rights 2.832
And Tails is running from USB drive "old" 0.277
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:331 1.508
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.926
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 58.361
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 25.498
And I take note of which tps features are available 0.898
Then a Tails persistence partition exists on USB drive "old" 0.689
And I shutdown Tails and wait for the computer to power off 7.170
After features/support/hooks.rb:331 0.487
After features/support/hooks.rb:100 0.006
Tags: @product
1:35.006
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.172
Then Tails is running from USB drive "old" 0.356
And all tps features are active 1.497
When I write some files expected to persist 1.586
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.202
And I take note of which tps features are available 0.216
And I shutdown Tails and wait for the computer to power off 8.116
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.170
After features/support/hooks.rb:331 0.360
After features/support/hooks.rb:100 0.006
Tags: @product
2:21.816
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 without a persistent partition and stopped at Tails Greeter's login screen 9.082
And I log in to a new session 14.663
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.761
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.943
Then the running Tails is installed on USB drive "to_upgrade" 17.833
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 0.910
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.705
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.540
Then all tps features from the old Tails version are active 1.126
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.009
And the expected persistent files created with the old Tails version are present in the filesystem 1.498
And all persistent directories from the old Tails version have safe access rights 2.103
After features/support/hooks.rb:331 0.681
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:3.976
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 with a persistent partition enabled and logged in 22.410
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.018
And Tor is ready 23.584
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.380
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.308
Given I shutdown Tails and wait for the computer to power off 19.860
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.666
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.399
And the file system changes introduced in version 6.2~testoverlayfs are present 0.244
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.213
When the network is plugged 0.019
And Tor is ready 20.597
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.665
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.947
Given I shutdown Tails and wait for the computer to power off 17.627
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.412
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.828
And the file system changes introduced in version 6.3~testoverlayfs are present 0.529
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.173
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.018
And Tor is ready 20.765
Then the Upgrader considers the system as up-to-date 0.129
# 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.042
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.438
After features/support/hooks.rb:331 0.805
After features/support/hooks.rb:100 0.085
Tags: @product @automatic_upgrade
28.125
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.766
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
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.018
And Tor is ready 19.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.431
After features/support/hooks.rb:331 0.661
After features/support/hooks.rb:100 0.000