Project Number Date
test_Tails_ISO_devel 4390 11 May 2026, 19:45

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:21.528 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.934
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.654
When I start Tails from USB drive "old" with network unplugged 44.943
Then the boot device has safe access rights 3.373
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:331 3.733
After features/support/hooks.rb:100 0.008
Tags: @product
1:37.234
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 59.355
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 28.681
And I take note of which tps features are available 0.908
Then a Tails persistence partition exists on USB drive "old" 0.698
And I shutdown Tails and wait for the computer to power off 7.237
After features/support/hooks.rb:331 0.171
After features/support/hooks.rb:100 0.008
Tags: @product
1:37.396
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.899
Then Tails is running from USB drive "old" 0.252
And all tps features are active 1.845
When I write some files expected to persist 1.676
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.589
And all persistent directories from the old Tails version have safe access rights 2.319
And I take note of which tps features are available 0.204
And I shutdown Tails and wait for the computer to power off 8.162
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.201
After features/support/hooks.rb:331 0.520
After features/support/hooks.rb:100 0.021
Tags: @product
2:18.356
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.633
And I log in to a new session 15.229
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.057
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.692
Then the running Tails is installed on USB drive "to_upgrade" 18.198
And I unplug USB drive "to_upgrade" 0.172
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 2.128
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.415
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.352
Then all tps features from the old Tails version are active 1.343
And Tails is running from USB drive "to_upgrade" 0.277
And the boot device has safe access rights 2.907
And the expected persistent files created with the old Tails version are present in the filesystem 1.264
And all persistent directories from the old Tails version have safe access rights 2.197
After features/support/hooks.rb:331 0.861
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:47.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.523
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.050
And Tor is ready 22.909
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.570
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.819
Given I shutdown Tails and wait for the computer to power off 7.182
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.383
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.419
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.224
When the network is plugged 0.031
And Tor is ready 21.473
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.417
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.453
Given I shutdown Tails and wait for the computer to power off 17.826
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.209
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.288
And the file system changes introduced in version 6.3~testoverlayfs are present 0.437
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.016
And Tor is ready 22.366
Then the Upgrader considers the system as up-to-date 0.109
# 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.241
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.444
After features/support/hooks.rb:331 1.096
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
36.659
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.812
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 27.113
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.395
After features/support/hooks.rb:331 0.537
After features/support/hooks.rb:100 0.000