Project Number Date
test_Tails_ISO_stable 6439 11 Jun 2026, 11:34

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 11:20.738 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:0.277
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.711
When I start Tails from USB drive "old" with network unplugged 42.205
Then the boot device has safe access rights 2.564
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:335 1.225
After features/support/hooks.rb:104 0.006
Tags: @product
1:29.128
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 54.153
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 25.670
And I take note of which tps features are available 0.320
Then a Tails persistence partition exists on USB drive "old" 0.493
And I shutdown Tails and wait for the computer to power off 8.187
After features/support/hooks.rb:335 0.274
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.768
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.464
Then Tails is running from USB drive "old" 0.342
And all tps features are active 1.205
When I write some files expected to persist 1.311
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.111
And I take note of which tps features are available 0.186
And I shutdown Tails and wait for the computer to power off 7.994
# 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" 12.493
After features/support/hooks.rb:335 0.542
After features/support/hooks.rb:104 0.006
Tags: @product
2:10.959
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 without a persistent partition and stopped at Tails Greeter's login screen 7.683
And I log in to a new session 13.201
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.772
And I plug USB drive "to_upgrade" 2.267
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.316
Then the running Tails is installed on USB drive "to_upgrade" 15.420
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.165
After features/support/hooks.rb:335 2.136
After features/support/hooks.rb:104 0.000
Tags: @product
1:9.962
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.030
Then all tps features from the old Tails version are active 0.984
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.533
And the expected persistent files created with the old Tails version are present in the filesystem 1.046
And all persistent directories from the old Tails version have safe access rights 2.084
After features/support/hooks.rb:335 0.785
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:40.953
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.389
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.520
When the network is plugged 0.022
And Tor is ready 11.985
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.513
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.224
Given I shutdown Tails and wait for the computer to power off 6.759
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.946
Then Tails is running version 6.2~testoverlayfs 0.030
And all tps features are active 1.094
And the file system changes introduced in version 6.2~testoverlayfs are present 0.253
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.196
# 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.255
When the network is plugged 0.014
And Tor is ready 10.072
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.083
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.480
Given I shutdown Tails and wait for the computer to power off 8.051
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.424
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 1.310
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.017
And Tor is ready 10.453
Then the Upgrader considers the system as up-to-date 10.544
# 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.317
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.418
After features/support/hooks.rb:335 0.890
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
20.687
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.579
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.629
After features/support/hooks.rb:335 1.139
After features/support/hooks.rb:104 0.000