Project Number Date
test_Tails_ISO_devel 4442 11 Jun 2026, 11:15

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:25.868 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:8.254
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.942
When I start Tails from USB drive "old" with network unplugged 49.607
Then the boot device has safe access rights 2.804
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:335 1.786
After features/support/hooks.rb:104 0.008
Tags: @product
1:25.217
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 54.204
Then Tails is running from USB drive "old" 0.285
And I create a persistent partition 25.424
And I take note of which tps features are available 0.350
Then a Tails persistence partition exists on USB drive "old" 0.638
And I shutdown Tails and wait for the computer to power off 4.242
After features/support/hooks.rb:335 0.108
After features/support/hooks.rb:104 0.008
Tags: @product
1:24.953
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.800
Then Tails is running from USB drive "old" 0.269
And all tps features are active 1.225
When I write some files expected to persist 1.293
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.305
And all persistent directories from the old Tails version have safe access rights 2.211
And I take note of which tps features are available 0.220
And I shutdown Tails and wait for the computer to power off 4.340
# 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.036
After features/support/hooks.rb:335 0.424
After features/support/hooks.rb:104 0.006
Tags: @product
2:11.867
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 8.343
And I log in to a new session 12.685
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.765
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.308
Then the running Tails is installed on USB drive "to_upgrade" 16.232
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:335 2.019
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.067
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.449
Then all tps features from the old Tails version are active 1.155
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 2.613
And the expected persistent files created with the old Tails version are present in the filesystem 1.440
And all persistent directories from the old Tails version have safe access rights 2.067
After features/support/hooks.rb:335 0.761
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:42.583
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.327
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
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.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.016
And Tor is ready 12.581
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.761
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.930
Given I shutdown Tails and wait for the computer to power off 7.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.800
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.145
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.209
When the network is plugged 0.022
And Tor is ready 10.211
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.696
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.369
Given I shutdown Tails and wait for the computer to power off 3.979
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.102
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.256
And the file system changes introduced in version 6.3~testoverlayfs are present 0.401
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.192
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.021
And Tor is ready 10.113
Then the Upgrader considers the system as up-to-date 10.714
# 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.371
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.437
After features/support/hooks.rb:335 0.961
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
21.924
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 7.721
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
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.069
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 11.855
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.906
After features/support/hooks.rb:335 0.888
After features/support/hooks.rb:104 0.000