Project Number Date
test_Tails_ISO_stable 6165 24 Feb 2026, 21:12

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:44.726 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:47.748
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.721
When I start Tails from USB drive "old" with network unplugged 1:12.056
Then the boot device has safe access rights 2.891
And Tails is running from USB drive "old" 0.275
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.237
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:331 1.739
After features/support/hooks.rb:100 0.009
Tags: @product
1:36.466
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:2.668
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 28.466
And I take note of which tps features are available 1.158
Then a Tails persistence partition exists on USB drive "old" 0.611
And I shutdown Tails and wait for the computer to power off 3.118
After features/support/hooks.rb:331 0.530
After features/support/hooks.rb:100 0.015
Tags: @product
1:42.681
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.549
Then Tails is running from USB drive "old" 0.320
And all tps features are active 1.955
When I write some files expected to persist 1.546
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.061
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 7.406
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.597
After features/support/hooks.rb:331 0.199
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.138
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 12.737
And I log in to a new session 12.433
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.205
And I plug USB drive "to_upgrade" 2.533
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.122
Then the running Tails is installed on USB drive "to_upgrade" 19.722
And I unplug USB drive "to_upgrade" 0.180
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:331 3.822
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.243
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.998
Then all tps features from the old Tails version are active 1.438
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 2.970
And the expected persistent files created with the old Tails version are present in the filesystem 1.260
And all persistent directories from the old Tails version have safe access rights 2.110
After features/support/hooks.rb:331 0.661
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:12.677
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 12.396
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.063
And Tor is ready 23.719
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.561
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.215
Given I shutdown Tails and wait for the computer to power off 20.950
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.574
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.940
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.176
# 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.247
When the network is plugged 0.055
And Tor is ready 23.480
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.555
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.375
Given I shutdown Tails and wait for the computer to power off 12.012
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.259
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 1.902
And the file system changes introduced in version 6.3~testoverlayfs are present 0.431
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.195
When the network is plugged 0.054
And Tor is ready 22.861
Then the Upgrader considers the system as up-to-date 0.115
# 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.358
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.492
After features/support/hooks.rb:331 0.943
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
32.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.009
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
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.060
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 20.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.558
After features/support/hooks.rb:331 1.287
After features/support/hooks.rb:100 0.000