Project Number Date
test_Tails_ISO_stable 6066 15 Jan 2026, 07:23

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:3.897 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:18.044
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.556
When I start Tails from USB drive "old" with network unplugged 58.647
Then the boot device has safe access rights 3.021
And Tails is running from USB drive "old" 0.267
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:331 3.610
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.117
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 54.649
Then Tails is running from USB drive "old" 0.260
And I create a persistent partition 23.947
And I take note of which tps features are available 0.661
Then a Tails persistence partition exists on USB drive "old" 0.538
And I shutdown Tails and wait for the computer to power off 8.004
After features/support/hooks.rb:331 0.356
After features/support/hooks.rb:100 0.014
Tags: @product
1:28.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.966
Then Tails is running from USB drive "old" 0.210
And all tps features are active 1.167
When I write some files expected to persist 1.158
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 1.974
And I take note of which tps features are available 0.195
And I shutdown Tails and wait for the computer to power off 7.885
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.494
After features/support/hooks.rb:331 0.240
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.258
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.504
And I log in to a new session 11.387
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.775
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.069
Then the running Tails is installed on USB drive "to_upgrade" 16.038
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:331 0.850
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.809
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.803
Then all tps features from the old Tails version are active 1.013
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 2.679
And the expected persistent files created with the old Tails version are present in the filesystem 1.048
And all persistent directories from the old Tails version have safe access rights 1.812
After features/support/hooks.rb:331 0.994
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:7.231
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.265
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.021
And Tor is ready 12.428
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.205
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.582
Given I shutdown Tails and wait for the computer to power off 6.959
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.965
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.090
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.208
When the network is plugged 0.019
And Tor is ready 39.702
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.369
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.989
Given I shutdown Tails and wait for the computer to power off 4.053
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.970
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.096
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.168
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.017
And Tor is ready 12.221
Then the Upgrader considers the system as up-to-date 10.713
# 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.646
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:331 0.742
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
19.811
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.632
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.584
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.227
After features/support/hooks.rb:331 0.988
After features/support/hooks.rb:100 0.000