Project Number Date
test_Tails_ISO_devel 4180 20 Jan 2026, 11:42

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 13:6.791 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:30.380
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 26.914
When I start Tails from USB drive "old" with network unplugged 58.417
Then the boot device has safe access rights 3.002
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:331 3.841
After features/support/hooks.rb:100 0.010
Tags: @product
1:37.235
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:0.735
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 26.772
And I take note of which tps features are available 1.125
Then a Tails persistence partition exists on USB drive "old" 0.631
And I shutdown Tails and wait for the computer to power off 7.474
After features/support/hooks.rb:331 0.250
After features/support/hooks.rb:100 0.010
Tags: @product
1:42.031
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.168
Then Tails is running from USB drive "old" 0.275
And all tps features are active 1.870
When I write some files expected to persist 1.337
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.348
And all persistent directories from the old Tails version have safe access rights 2.219
And I take note of which tps features are available 0.495
And I shutdown Tails and wait for the computer to power off 7.399
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.544
After features/support/hooks.rb:331 0.368
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.918
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.744
And I log in to a new session 9.473
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.316
And I plug USB drive "to_upgrade" 3.615
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.077
Then the running Tails is installed on USB drive "to_upgrade" 18.268
And I unplug USB drive "to_upgrade" 0.178
And I unplug USB drive "__internal" 0.244
After features/support/hooks.rb:331 3.971
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.697
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.689
Then all tps features from the old Tails version are active 1.357
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 2.968
And the expected persistent files created with the old Tails version are present in the filesystem 1.512
And all persistent directories from the old Tails version have safe access rights 2.684
After features/support/hooks.rb:331 0.750
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:18.485
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.476
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
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.258
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.053
And Tor is ready 13.917
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.577
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.859
Given I shutdown Tails and wait for the computer to power off 7.460
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.714
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.085
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.181
# 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.231
When the network is plugged 0.069
And Tor is ready 39.964
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.678
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.933
Given I shutdown Tails and wait for the computer to power off 3.131
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.458
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.054
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.169
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.052
And Tor is ready 12.563
Then the Upgrader considers the system as up-to-date 0.123
# 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 5.959
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.584
After features/support/hooks.rb:331 1.031
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
21.043
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.882
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 10.081
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.692
After features/support/hooks.rb:331 0.825
After features/support/hooks.rb:100 0.000