Project Number Date
test_Tails_ISO_stable 6354 05 May 2026, 16:10

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:29.197 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:4.111
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.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.736
When I start Tails from USB drive "old" with network unplugged 45.835
Then the boot device has safe access rights 2.742
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 3.489
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.753
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 55.109
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 24.715
And I take note of which tps features are available 0.893
Then a Tails persistence partition exists on USB drive "old" 0.790
And I shutdown Tails and wait for the computer to power off 6.968
After features/support/hooks.rb:331 0.204
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.480
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.909
Then Tails is running from USB drive "old" 0.233
And all tps features are active 1.137
When I write some files expected to persist 1.205
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.161
And all persistence configuration files have safe access rights 0.506
And all persistent directories from the old Tails version have safe access rights 1.967
And I take note of which tps features are available 0.156
And I shutdown Tails and wait for the computer to power off 8.647
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.493
After features/support/hooks.rb:331 0.347
After features/support/hooks.rb:100 0.006
Tags: @product
2:13.216
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 without a persistent partition and stopped at Tails Greeter's login screen 8.541
And I log in to a new session 12.542
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.046
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.834
Then the running Tails is installed on USB drive "to_upgrade" 16.746
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 2.031
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.159
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.281
Then all tps features from the old Tails version are active 1.129
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 3.182
And the expected persistent files created with the old Tails version are present in the filesystem 1.246
And all persistent directories from the old Tails version have safe access rights 1.995
After features/support/hooks.rb:331 0.618
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:34.949
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.423
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.338
When the network is plugged 0.017
And Tor is ready 21.067
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.509
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.900
Given I shutdown Tails and wait for the computer to power off 20.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.763
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.102
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.196
When the network is plugged 0.015
And Tor is ready 21.872
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.529
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.663
Given I shutdown Tails and wait for the computer to power off 13.637
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.333
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.087
And the file system changes introduced in version 6.3~testoverlayfs are present 0.411
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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.015
And Tor is ready 20.876
Then the Upgrader considers the system as up-to-date 0.103
# 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.831
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.440
After features/support/hooks.rb:331 1.004
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
26.528
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 7.875
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 17.757
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.452
After features/support/hooks.rb:331 0.994
After features/support/hooks.rb:100 0.000