Project Number Date
test_Tails_ISO_stable 6398 22 May 2026, 11:40

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:1.835 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:9.163
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.109
And I create a 7200 MiB disk named "old" 0.015
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 13.523
When I start Tails from USB drive "old" with network unplugged 51.078
Then the boot device has safe access rights 2.658
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:335 3.459
After features/support/hooks.rb:104 0.007
Tags: @product
1:32.195
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 "old" with network unplugged and I login 57.797
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 25.823
And I take note of which tps features are available 0.421
Then a Tails persistence partition exists on USB drive "old" 0.573
And I shutdown Tails and wait for the computer to power off 7.239
After features/support/hooks.rb:335 0.181
After features/support/hooks.rb:104 0.009
Tags: @product
1:40.620
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.016
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.484
Then Tails is running from USB drive "old" 0.249
And all tps features are active 1.235
When I write some files expected to persist 1.179
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 2.277
And I take note of which tps features are available 0.245
And I shutdown Tails and wait for the computer to power off 17.507
# 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.817
After features/support/hooks.rb:335 0.224
After features/support/hooks.rb:104 0.006
Tags: @product
2:14.049
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 without a persistent partition and stopped at Tails Greeter's login screen 7.971
And I log in to a new session 14.467
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.681
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.097
Then the running Tails is installed on USB drive "to_upgrade" 16.225
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:335 3.650
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.747
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.363
Then all tps features from the old Tails version are active 1.285
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.974
And the expected persistent files created with the old Tails version are present in the filesystem 1.451
And all persistent directories from the old Tails version have safe access rights 2.358
After features/support/hooks.rb:335 1.023
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:47.840
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.610
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.016
And Tor is ready 14.850
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.822
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.833
Given I shutdown Tails and wait for the computer to power off 6.913
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.201
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.120
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.232
When the network is plugged 0.015
And Tor is ready 11.667
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.699
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.479
Given I shutdown Tails and wait for the computer to power off 4.204
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.386
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 1.306
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.018
And Tor is ready 12.033
Then the Upgrader considers the system as up-to-date 10.591
# 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.263
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:335 1.120
After features/support/hooks.rb:104 0.047
Tags: @product @automatic_upgrade
22.219
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 7.944
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.313
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.580
After features/support/hooks.rb:335 1.083
After features/support/hooks.rb:104 0.000