Project Number Date
test_Tails_ISO_stable 6662 14 Sep 2026, 07:21

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:46.695 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:6.923
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.049
When I start Tails from USB drive "old" with network unplugged 50.355
Then the boot device has safe access rights 1.853
And Tails is running from USB drive "old" 0.164
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.031
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.558
After features/support/hooks.rb:108 0.005
Tags: @product
1:17.143
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 45.766
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 22.083
And I take note of which tps features are available 5.916
Then a Tails persistence partition exists on USB drive "old" 0.458
And I shutdown Tails and wait for the computer to power off 2.616
After features/support/hooks.rb:339 0.241
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.620
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.514
Then Tails is running from USB drive "old" 0.219
And all tps features are active 6.542
When I write some files expected to persist 1.012
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.181
And all persistent directories from the old Tails version have safe access rights 1.473
And I take note of which tps features are available 5.731
And I shutdown Tails and wait for the computer to power off 2.514
# 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.144
After features/support/hooks.rb:339 0.180
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.233
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 without a persistent partition and stopped at Tails Greeter's login screen 8.252
And I log in to a new session 10.056
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.693
And I plug USB drive "to_upgrade" 2.176
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.351
Then the running Tails is installed on USB drive "to_upgrade" 17.464
And I unplug USB drive "to_upgrade" 0.112
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 1.651
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.957
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.447
Then all tps features from the old Tails version are active 1.009
And Tails is running from USB drive "to_upgrade" 0.203
And the boot device has safe access rights 1.833
And the expected persistent files created with the old Tails version are present in the filesystem 0.708
And all persistent directories from the old Tails version have safe access rights 1.675
After features/support/hooks.rb:339 0.676
After features/support/hooks.rb:108 0.005
3:21.339
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.007
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.188
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.025
And Tor is ready 11.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.029
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.041
Given I shutdown Tails and wait for the computer to power off 5.221
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.001
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.706
And the file system changes introduced in version 6.2~testoverlayfs are present 0.162
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.099
# 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.178
When the network is plugged 0.035
And Tor is ready 10.081
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.371
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.432
Given I shutdown Tails and wait for the computer to power off 2.557
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.715
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.519
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.098
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.181
When the network is plugged 0.034
And Tor is ready 10.034
Then the Upgrader considers the system as up-to-date 0.085
# 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.193
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.359
After features/support/hooks.rb:339 0.976
After features/support/hooks.rb:108 0.021
19.477
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.860
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.035
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.278
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.013
After features/support/hooks.rb:339 0.642
After features/support/hooks.rb:108 0.000