Project Number Date
test_Tails_ISO_stable 6045 08 Jan 2026, 19:17

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:6.486 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:13.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.585
When I start Tails from USB drive "old" with network unplugged 53.758
Then the boot device has safe access rights 3.425
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:331 3.932
After features/support/hooks.rb:100 0.039
Tags: @product
1:32.426
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 57.170
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 26.244
And I take note of which tps features are available 0.777
Then a Tails persistence partition exists on USB drive "old" 0.581
And I shutdown Tails and wait for the computer to power off 7.243
After features/support/hooks.rb:331 0.426
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.703
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.489
Then Tails is running from USB drive "old" 0.304
And all tps features are active 1.193
When I write some files expected to persist 1.380
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.167
And I take note of which tps features are available 0.173
And I shutdown Tails and wait for the computer to power off 7.307
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.039
After features/support/hooks.rb:331 0.164
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.060
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.847
And I log in to a new session 13.429
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.346
And I plug USB drive "to_upgrade" 2.357
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.489
Then the running Tails is installed on USB drive "to_upgrade" 18.229
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.157
After features/support/hooks.rb:331 3.864
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.218
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.362
Then all tps features from the old Tails version are active 1.258
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 2.879
And the expected persistent files created with the old Tails version are present in the filesystem 1.273
And all persistent directories from the old Tails version have safe access rights 2.051
After features/support/hooks.rb:331 0.530
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
3:53.828
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.008
And no SquashFS delta is installed 0.136
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.014
And Tor is ready 13.913
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.286
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.737
Given I shutdown Tails and wait for the computer to power off 9.649
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.032
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.365
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.250
When the network is plugged 0.020
And Tor is ready 11.337
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.152
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.702
Given I shutdown Tails and wait for the computer to power off 8.469
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.166
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.275
And the file system changes introduced in version 6.3~testoverlayfs are present 0.647
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.182
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.025
And Tor is ready 12.207
Then the Upgrader considers the system as up-to-date 10.700
# 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.957
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.544
After features/support/hooks.rb:331 1.198
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
21.489
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.700
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.854
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.596
After features/support/hooks.rb:331 0.742
After features/support/hooks.rb:100 0.000