Project Number Date
test_Tails_ISO_devel 4393 13 May 2026, 02:30

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:28.405 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:6.410
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.495
When I start Tails from USB drive "old" with network unplugged 46.941
Then the boot device has safe access rights 3.124
And Tails is running from USB drive "old" 0.270
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.237
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:335 3.716
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.517
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login 53.845
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 25.199
And I take note of which tps features are available 0.435
Then a Tails persistence partition exists on USB drive "old" 0.638
And I shutdown Tails and wait for the computer to power off 7.009
After features/support/hooks.rb:335 0.368
After features/support/hooks.rb:104 0.008
Tags: @product
1:30.536
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.203
Then Tails is running from USB drive "old" 0.243
And all tps features are active 1.147
When I write some files expected to persist 1.397
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.318
And all persistence configuration files have safe access rights 0.455
And all persistent directories from the old Tails version have safe access rights 2.259
And I take note of which tps features are available 0.258
And I shutdown Tails and wait for the computer to power off 8.496
# 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.699
After features/support/hooks.rb:335 0.343
After features/support/hooks.rb:104 0.010
Tags: @product
2:11.375
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.899
And I log in to a new session 12.063
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.688
And I plug USB drive "to_upgrade" 2.284
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.569
Then the running Tails is installed on USB drive "to_upgrade" 16.548
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:335 4.084
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.370
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.982
Then all tps features from the old Tails version are active 0.997
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.718
And the expected persistent files created with the old Tails version are present in the filesystem 1.333
And all persistent directories from the old Tails version have safe access rights 2.037
After features/support/hooks.rb:335 0.852
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:41.980
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.084
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.023
And Tor is ready 13.283
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.223
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.111
Given I shutdown Tails and wait for the computer to power off 9.938
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.996
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.156
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.240
When the network is plugged 0.020
And Tor is ready 10.499
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.617
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.832
Given I shutdown Tails and wait for the computer to power off 8.136
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.820
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.382
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.024
And Tor is ready 10.143
Then the Upgrader considers the system as up-to-date 10.480
# 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.221
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.358
After features/support/hooks.rb:335 0.965
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
20.213
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.387
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.077
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.342
After features/support/hooks.rb:335 0.998
After features/support/hooks.rb:104 0.000