Project Number Date
test_Tails_ISO_stable 6640 05 Sep 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:43.282 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:12.619
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.111
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.554
When I start Tails from USB drive "old" with network unplugged 55.361
Then the boot device has safe access rights 1.949
And Tails is running from USB drive "old" 0.209
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.463
After features/support/hooks.rb:108 0.006
Tags: @product
1:23.207
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 50.172
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 23.173
And I take note of which tps features are available 6.186
Then a Tails persistence partition exists on USB drive "old" 0.552
And I shutdown Tails and wait for the computer to power off 2.807
After features/support/hooks.rb:339 0.103
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.957
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.123
Then Tails is running from USB drive "old" 0.191
And all tps features are active 7.851
When I write some files expected to persist 1.137
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.251
And all persistent directories from the old Tails version have safe access rights 1.616
And I take note of which tps features are available 6.788
And I shutdown Tails and wait for the computer to power off 4.178
# 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.524
After features/support/hooks.rb:339 0.390
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.491
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.794
And I log in to a new session 11.507
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.854
And I plug USB drive "to_upgrade" 2.256
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.803
Then the running Tails is installed on USB drive "to_upgrade" 19.044
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 1.542
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.882
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.168
Then all tps features from the old Tails version are active 1.408
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.603
And the expected persistent files created with the old Tails version are present in the filesystem 1.378
And all persistent directories from the old Tails version have safe access rights 1.982
After features/support/hooks.rb:339 0.903
After features/support/hooks.rb:108 0.045
Tags: @product @automatic_upgrade
3:42.490
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
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.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.325
When the network is plugged 0.032
And Tor is ready 13.550
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.501
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.481
Given I shutdown Tails and wait for the computer to power off 6.907
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.150
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.009
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.172
When the network is plugged 0.023
And Tor is ready 10.539
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.900
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.830
Given I shutdown Tails and wait for the computer to power off 4.055
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.184
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.772
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.058
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.038
And Tor is ready 10.640
Then the Upgrader considers the system as up-to-date 0.099
# 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 3.586
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:339 0.895
After features/support/hooks.rb:108 0.049
Tags: @product @automatic_upgrade
19.634
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.956
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 9.852
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.461
After features/support/hooks.rb:339 0.521
After features/support/hooks.rb:108 0.000