Project Number Date
test_Tails_ISO_devel 4430 04 Jun 2026, 11:04

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 10:56.416 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.471
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.043
When I start Tails from USB drive "old" with network unplugged 47.378
Then the boot device has safe access rights 2.301
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:335 3.719
After features/support/hooks.rb:104 0.029
Tags: @product
1:23.790
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 50.493
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 24.080
And I take note of which tps features are available 0.320
Then a Tails persistence partition exists on USB drive "old" 0.582
And I shutdown Tails and wait for the computer to power off 7.924
After features/support/hooks.rb:335 0.549
After features/support/hooks.rb:104 0.006
Tags: @product
1:23.847
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.959
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.051
When I write some files expected to persist 1.205
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.137
And all persistence configuration files have safe access rights 0.249
And all persistent directories from the old Tails version have safe access rights 1.941
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 8.177
# 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" 11.672
After features/support/hooks.rb:335 0.440
After features/support/hooks.rb:104 0.006
Tags: @product
2:9.008
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 without a persistent partition and stopped at Tails Greeter's login screen 7.849
And I log in to a new session 11.991
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.736
And I plug USB drive "to_upgrade" 2.196
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.012
Then the running Tails is installed on USB drive "to_upgrade" 14.919
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.170
After features/support/hooks.rb:335 1.937
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.531
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.020
Then all tps features from the old Tails version are active 1.054
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.333
And the expected persistent files created with the old Tails version are present in the filesystem 1.026
And all persistent directories from the old Tails version have safe access rights 1.817
After features/support/hooks.rb:335 0.691
After features/support/hooks.rb:104 0.005
3:28.869
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.123
And no SquashFS delta is installed 0.084
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.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.014
And Tor is ready 11.938
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.997
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.374
Given I shutdown Tails and wait for the computer to power off 10.653
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.901
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.015
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.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.119
# 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.191
When the network is plugged 0.016
And Tor is ready 10.016
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.129
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.660
Given I shutdown Tails and wait for the computer to power off 2.661
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.699
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.092
And the file system changes introduced in version 6.3~testoverlayfs are present 0.320
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.014
And Tor is ready 10.188
Then the Upgrader considers the system as up-to-date 10.599
# 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.138
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:335 1.081
After features/support/hooks.rb:104 0.011
19.898
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 7.178
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 8.562
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.841
After features/support/hooks.rb:335 0.837
After features/support/hooks.rb:104 0.000