Project Number Date
test_Tails_ISO_stable 6306 17 Apr 2026, 11:41

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:20.511 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:16.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.680
When I start Tails from USB drive "old" with network unplugged 57.310
Then the boot device has safe access rights 2.877
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.158
After features/support/hooks.rb:331 1.184
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.681
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 55.091
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 23.837
And I take note of which tps features are available 0.724
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 8.124
After features/support/hooks.rb:331 0.192
After features/support/hooks.rb:100 0.019
Tags: @product
1:30.282
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.802
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.242
When I write some files expected to persist 1.418
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.476
And all persistent directories from the old Tails version have safe access rights 2.037
And I take note of which tps features are available 0.193
And I shutdown Tails and wait for the computer to power off 8.318
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.157
After features/support/hooks.rb:331 0.548
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.885
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.491
And I log in to a new session 16.415
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.783
And I plug USB drive "to_upgrade" 2.304
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.153
Then the running Tails is installed on USB drive "to_upgrade" 16.457
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 3.075
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.139
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.904
Then all tps features from the old Tails version are active 0.917
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.669
And the expected persistent files created with the old Tails version are present in the filesystem 1.275
And all persistent directories from the old Tails version have safe access rights 2.062
After features/support/hooks.rb:331 0.652
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
5:1.172
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 8.788
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.394
When the network is plugged 0.016
And Tor is ready 23.826
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.421
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.526
Given I shutdown Tails and wait for the computer to power off 21.198
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.428
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.107
And the file system changes introduced in version 6.2~testoverlayfs are present 0.182
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.196
When the network is plugged 0.020
And Tor is ready 20.683
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.383
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.043
Given I shutdown Tails and wait for the computer to power off 17.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.129
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.420
And the file system changes introduced in version 6.3~testoverlayfs are present 0.414
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.039
And Tor is ready 39.507
Then the Upgrader considers the system as up-to-date 0.170
# 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.256
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:331 0.885
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.673
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.665
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 18.181
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.404
After features/support/hooks.rb:331 0.623
After features/support/hooks.rb:100 0.000