Project Number Date
test_Tails_ISO_stable 6407 27 May 2026, 12:14

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 11:32.797 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:1.799
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 14.213
When I start Tails from USB drive "old" with network unplugged 42.577
Then the boot device has safe access rights 2.933
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.149
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:335 1.358
After features/support/hooks.rb:104 0.007
Tags: @product
1:29.592
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 54.609
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 25.493
And I take note of which tps features are available 0.370
Then a Tails persistence partition exists on USB drive "old" 0.541
And I shutdown Tails and wait for the computer to power off 8.236
After features/support/hooks.rb:335 0.305
After features/support/hooks.rb:104 0.008
Tags: @product
1:30.962
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.127
Then Tails is running from USB drive "old" 0.233
And all tps features are active 1.399
When I write some files expected to persist 1.542
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.348
And all persistent directories from the old Tails version have safe access rights 2.486
And I take note of which tps features are available 0.207
And I shutdown Tails and wait for the computer to power off 8.451
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.904
After features/support/hooks.rb:335 0.454
After features/support/hooks.rb:104 0.007
Tags: @product
2:14.557
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 8.653
And I log in to a new session 14.014
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.796
And I plug USB drive "to_upgrade" 2.303
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.152
Then the running Tails is installed on USB drive "to_upgrade" 16.330
And I unplug USB drive "to_upgrade" 0.164
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:335 2.328
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.452
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.343
Then all tps features from the old Tails version are active 1.082
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.631
And the expected persistent files created with the old Tails version are present in the filesystem 1.231
And all persistent directories from the old Tails version have safe access rights 1.880
After features/support/hooks.rb:335 0.796
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:42.384
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.292
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.019
And Tor is ready 12.419
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.431
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.520
Given I shutdown Tails and wait for the computer to power off 7.146
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.490
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.184
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
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.144
# 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.356
When the network is plugged 0.016
And Tor is ready 10.219
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.003
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.398
Given I shutdown Tails and wait for the computer to power off 8.173
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.012
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.207
And the file system changes introduced in version 6.3~testoverlayfs are present 0.347
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.016
And Tor is ready 10.275
Then the Upgrader considers the system as up-to-date 10.599
# 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 3.876
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.363
After features/support/hooks.rb:335 1.068
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
21.049
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.426
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.013
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.196
After features/support/hooks.rb:335 0.680
After features/support/hooks.rb:104 0.000