Project Number Date
test_Tails_ISO_stable 6315 21 Apr 2026, 13: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:58.744 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:1.849
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.955
When I start Tails from USB drive "old" with network unplugged 42.951
Then the boot device has safe access rights 3.096
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:331 1.402
After features/support/hooks.rb:100 0.009
Tags: @product
1:30.820
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 56.518
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 24.106
And I take note of which tps features are available 0.764
Then a Tails persistence partition exists on USB drive "old" 0.633
And I shutdown Tails and wait for the computer to power off 8.417
After features/support/hooks.rb:331 0.591
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.878
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 with persistence enabled 1:8.964
Then Tails is running from USB drive "old" 0.275
And all tps features are active 1.193
When I write some files expected to persist 1.382
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 1.807
And I take note of which tps features are available 0.181
And I shutdown Tails and wait for the computer to power off 4.091
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.328
After features/support/hooks.rb:331 0.489
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.733
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 8.194
And I log in to a new session 12.851
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.754
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.366
Then the running Tails is installed on USB drive "to_upgrade" 16.062
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:331 0.805
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.051
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.298
Then all tps features from the old Tails version are active 0.988
And Tails is running from USB drive "to_upgrade" 0.274
And the boot device has safe access rights 2.719
And the expected persistent files created with the old Tails version are present in the filesystem 1.418
And all persistent directories from the old Tails version have safe access rights 2.255
After features/support/hooks.rb:331 0.812
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:53.922
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 9.084
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.028
And Tor is ready 22.524
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.526
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.269
Given I shutdown Tails and wait for the computer to power off 20.904
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.943
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.454
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.276
When the network is plugged 0.020
And Tor is ready 20.939
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.416
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.662
Given I shutdown Tails and wait for the computer to power off 17.875
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.424
Then Tails is running version 6.3~testoverlayfs 0.035
And all tps features are active 1.435
And the file system changes introduced in version 6.3~testoverlayfs are present 0.543
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.231
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.019
And Tor is ready 22.831
Then the Upgrader considers the system as up-to-date 0.122
# 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.065
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.470
After features/support/hooks.rb:331 1.079
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
28.487
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 8.833
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
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.040
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 18.698
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.538
After features/support/hooks.rb:331 0.994
After features/support/hooks.rb:100 0.000