Project Number Date
test_Tails_ISO_stable 6358 07 May 2026, 18:37

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 12:24.782 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:0.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 13.765
When I start Tails from USB drive "old" with network unplugged 41.969
Then the boot device has safe access rights 2.892
And Tails is running from USB drive "old" 0.262
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:331 3.683
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.223
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 55.078
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 24.152
And I take note of which tps features are available 0.673
Then a Tails persistence partition exists on USB drive "old" 0.520
And I shutdown Tails and wait for the computer to power off 8.466
After features/support/hooks.rb:331 0.213
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.076
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.556
Then Tails is running from USB drive "old" 0.281
And all tps features are active 1.410
When I write some files expected to persist 1.341
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 1.963
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 3.946
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.745
After features/support/hooks.rb:331 0.305
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.177
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.031
And I log in to a new session 13.678
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.780
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.465
Then the running Tails is installed on USB drive "to_upgrade" 15.557
And I unplug USB drive "to_upgrade" 0.180
And I unplug USB drive "__internal" 0.243
After features/support/hooks.rb:331 2.509
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.266
Then all tps features from the old Tails version are active 1.103
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.618
And the expected persistent files created with the old Tails version are present in the filesystem 1.107
And all persistent directories from the old Tails version have safe access rights 1.933
After features/support/hooks.rb:331 0.836
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:42.336
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 8.272
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.371
When the network is plugged 0.020
And Tor is ready 21.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.441
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.938
Given I shutdown Tails and wait for the computer to power off 20.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.913
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.271
And the file system changes introduced in version 6.2~testoverlayfs are present 0.261
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.122
# 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.264
When the network is plugged 0.015
And Tor is ready 21.415
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.382
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.384
Given I shutdown Tails and wait for the computer to power off 17.509
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.147
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.219
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.171
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.372
When the network is plugged 0.131
And Tor is ready 20.932
Then the Upgrader considers the system as up-to-date 0.106
# 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.491
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.427
After features/support/hooks.rb:331 0.710
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
26.117
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 7.465
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 17.901
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.390
After features/support/hooks.rb:331 0.605
After features/support/hooks.rb:100 0.000