Project Number Date
test_Tails_ISO_devel 4500 19 Jul 2026, 12:10

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 12:1.015 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:2.370
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.259
When I start Tails from USB drive "old" with network unplugged 43.803
Then the boot device has safe access rights 2.526
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.742
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.557
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 54.962
Then Tails is running from USB drive "old" 0.280
And I create a persistent partition 25.609
And I take note of which tps features are available 4.844
Then a Tails persistence partition exists on USB drive "old" 0.535
And I shutdown Tails and wait for the computer to power off 8.240
After features/support/hooks.rb:339 0.298
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.909
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.317
Then Tails is running from USB drive "old" 0.275
And all tps features are active 6.208
When I write some files expected to persist 1.339
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.263
And all persistence configuration files have safe access rights 0.337
And all persistent directories from the old Tails version have safe access rights 2.186
And I take note of which tps features are available 4.096
And I shutdown Tails and wait for the computer to power off 4.422
# 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.413
After features/support/hooks.rb:339 0.450
After features/support/hooks.rb:108 0.007
Tags: @product
2:11.976
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 7.201
And I log in to a new session 13.443
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.706
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.187
Then the running Tails is installed on USB drive "to_upgrade" 15.919
And I unplug USB drive "to_upgrade" 0.152
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 2.756
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.979
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.590
Then all tps features from the old Tails version are active 0.879
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.673
And the expected persistent files created with the old Tails version are present in the filesystem 1.187
And all persistent directories from the old Tails version have safe access rights 2.341
After features/support/hooks.rb:339 0.842
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
3:57.101
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.182
And no SquashFS delta is installed 0.046
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.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.340
When the network is plugged 0.017
And Tor is ready 13.588
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.946
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.239
Given I shutdown Tails and wait for the computer to power off 5.424
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.755
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.421
And the file system changes introduced in version 6.2~testoverlayfs are present 0.261
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.151
# 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.016
And Tor is ready 10.136
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.480
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.402
Given I shutdown Tails and wait for the computer to power off 8.013
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.155
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 5.232
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.014
And Tor is ready 11.477
Then the Upgrader considers the system as up-to-date 10.509
# 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.429
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.906
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
21.120
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 7.486
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.051
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.021
And Tor is ready 9.902
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.392
After features/support/hooks.rb:339 0.652
After features/support/hooks.rb:108 0.000