Project Number Date
test_Tails_ISO_devel 4403 19 May 2026, 14:37

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:16.625 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:15.625
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.015
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.338
When I start Tails from USB drive "old" with network unplugged 56.364
Then the boot device has safe access rights 3.051
And Tails is running from USB drive "old" 0.280
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:335 3.487
After features/support/hooks.rb:104 0.016
Tags: @product
1:36.652
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 58.802
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 29.079
And I take note of which tps features are available 0.501
Then a Tails persistence partition exists on USB drive "old" 0.727
And I shutdown Tails and wait for the computer to power off 7.124
After features/support/hooks.rb:335 0.230
After features/support/hooks.rb:104 0.011
Tags: @product
1:31.127
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.996
Then Tails is running from USB drive "old" 0.319
And all tps features are active 1.332
When I write some files expected to persist 1.647
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.294
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.545
And I take note of which tps features are available 0.233
And I shutdown Tails and wait for the computer to power off 4.270
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 13.036
After features/support/hooks.rb:335 0.300
After features/support/hooks.rb:104 0.040
Tags: @product
2:15.946
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.372
And I log in to a new session 14.338
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.992
And I plug USB drive "to_upgrade" 2.260
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.314
Then the running Tails is installed on USB drive "to_upgrade" 17.310
And I unplug USB drive "to_upgrade" 0.179
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:335 2.299
After features/support/hooks.rb:104 0.000
Tags: @product
1:16.626
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.031
Then all tps features from the old Tails version are active 1.159
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 2.739
And the expected persistent files created with the old Tails version are present in the filesystem 1.179
And all persistent directories from the old Tails version have safe access rights 2.162
After features/support/hooks.rb:335 0.737
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
3:59.663
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.075
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.016
And Tor is ready 14.197
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.125
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.425
Given I shutdown Tails and wait for the computer to power off 9.615
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.938
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.264
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.220
When the network is plugged 0.017
And Tor is ready 10.440
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.129
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.394
Given I shutdown Tails and wait for the computer to power off 8.125
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.642
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.320
And the file system changes introduced in version 6.3~testoverlayfs are present 0.383
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.194
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.017
And Tor is ready 12.864
Then the Upgrader considers the system as up-to-date 10.650
# 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.363
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.424
After features/support/hooks.rb:335 0.918
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
20.983
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
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.036
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.303
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.157
After features/support/hooks.rb:335 0.820
After features/support/hooks.rb:104 0.000