Project Number Date
test_Tails_ISO_stable 6174 26 Feb 2026, 12: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 15:39.968 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.118
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 32.114
When I start Tails from USB drive "old" with network unplugged 1:8.668
Then the boot device has safe access rights 3.136
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:331 1.860
After features/support/hooks.rb:100 0.008
Tags: @product
1:48.123
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:4.666
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 28.556
And I take note of which tps features are available 4.634
Then a Tails persistence partition exists on USB drive "old" 2.901
And I shutdown Tails and wait for the computer to power off 6.877
After features/support/hooks.rb:331 0.407
After features/support/hooks.rb:100 0.010
Tags: @product
1:51.085
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:16.932
Then Tails is running from USB drive "old" 0.721
And all tps features are active 2.160
When I write some files expected to persist 1.555
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.338
And all persistent directories from the old Tails version have safe access rights 2.432
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 7.654
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.399
After features/support/hooks.rb:331 0.306
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.077
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.400
And I log in to a new session 14.520
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.260
And I plug USB drive "to_upgrade" 2.592
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.397
Then the running Tails is installed on USB drive "to_upgrade" 20.501
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:331 2.548
After features/support/hooks.rb:100 0.000
Tags: @product
1:29.710
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.966
Then all tps features from the old Tails version are active 1.588
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 3.083
And the expected persistent files created with the old Tails version are present in the filesystem 1.355
And all persistent directories from the old Tails version have safe access rights 2.208
After features/support/hooks.rb:331 0.771
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:32.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.704
And no SquashFS delta is installed 0.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 1.154
And Tor is ready 26.928
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.571
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.293
Given I shutdown Tails and wait for the computer to power off 20.641
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:30.652
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.340
And the file system changes introduced in version 6.2~testoverlayfs are present 0.267
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.172
# 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.256
When the network is plugged 0.067
And Tor is ready 22.302
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.630
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.799
Given I shutdown Tails and wait for the computer to power off 18.071
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:28.950
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.318
And the file system changes introduced in version 6.3~testoverlayfs are present 0.420
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.229
When the network is plugged 0.056
And Tor is ready 22.573
Then the Upgrader considers the system as up-to-date 0.116
# 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 6.174
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.463
After features/support/hooks.rb:331 1.065
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
33.125
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.738
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 21.405
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.579
After features/support/hooks.rb:331 1.174
After features/support/hooks.rb:100 0.000