Project Number Date
test_Tails_ISO_stable 6462 18 Jun 2026, 11:48

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:7.220 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:3.930
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.025
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 13.794
When I start Tails from USB drive "old" with network unplugged 45.415
Then the boot device has safe access rights 2.785
And Tails is running from USB drive "old" 0.266
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 3.701
After features/support/hooks.rb:108 0.025
Tags: @product
1:31.699
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 54.592
Then Tails is running from USB drive "old" 0.269
And I create a persistent partition 24.593
And I take note of which tps features are available 4.427
Then a Tails persistence partition exists on USB drive "old" 0.530
And I shutdown Tails and wait for the computer to power off 7.116
After features/support/hooks.rb:339 0.188
After features/support/hooks.rb:108 0.057
Tags: @product
1:41.013
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given a computer 0.138
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.432
Then Tails is running from USB drive "old" 0.248
And all tps features are active 5.087
When I write some files expected to persist 1.216
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.176
And I take note of which tps features are available 4.342
And I shutdown Tails and wait for the computer to power off 8.290
# 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.521
After features/support/hooks.rb:339 0.275
After features/support/hooks.rb:108 0.028
Tags: @product
2:11.230
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.377
And I log in to a new session 12.908
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.807
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.806
Then the running Tails is installed on USB drive "to_upgrade" 14.830
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:339 2.187
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.866
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.916
Then all tps features from the old Tails version are active 1.000
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.441
And the expected persistent files created with the old Tails version are present in the filesystem 1.195
And all persistent directories from the old Tails version have safe access rights 1.826
After features/support/hooks.rb:339 0.866
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
4:4.456
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.040
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.802
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
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.349
When the network is plugged 0.030
And Tor is ready 12.245
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.404
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.168
Given I shutdown Tails and wait for the computer to power off 9.911
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.832
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.885
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.184
When the network is plugged 0.014
And Tor is ready 11.334
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.221
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.887
Given I shutdown Tails and wait for the computer to power off 8.232
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.376
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.447
And the file system changes introduced in version 6.3~testoverlayfs are present 0.330
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.015
And Tor is ready 12.527
Then the Upgrader considers the system as up-to-date 10.620
# 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.660
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.477
After features/support/hooks.rb:339 1.017
After features/support/hooks.rb:108 0.048
Tags: @product @automatic_upgrade
20.024
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.230
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.051
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 9.915
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.529
After features/support/hooks.rb:339 0.768
After features/support/hooks.rb:108 0.000