Project Number Date
test_Tails_ISO_devel 4512 25 Jul 2026, 01:39

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:33.233 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.048
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.061
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" 13.399
When I start Tails from USB drive "old" with network unplugged 46.444
Then the boot device has safe access rights 2.495
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 1.284
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.253
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 53.074
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 25.023
And I take note of which tps features are available 4.088
Then a Tails persistence partition exists on USB drive "old" 0.706
And I shutdown Tails and wait for the computer to power off 4.076
After features/support/hooks.rb:339 0.613
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.387
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.774
Then Tails is running from USB drive "old" 0.288
And all tps features are active 5.246
When I write some files expected to persist 1.420
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.341
And all persistent directories from the old Tails version have safe access rights 2.117
And I take note of which tps features are available 4.399
And I shutdown Tails and wait for the computer to power off 4.183
# 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.389
After features/support/hooks.rb:339 0.485
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.119
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.857
And I log in to a new session 12.013
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.736
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.668
Then the running Tails is installed on USB drive "to_upgrade" 15.358
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 2.143
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.032
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:4.218
Then all tps features from the old Tails version are active 1.038
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.515
And the expected persistent files created with the old Tails version are present in the filesystem 0.994
And all persistent directories from the old Tails version have safe access rights 1.955
After features/support/hooks.rb:339 0.752
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:43.957
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.842
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.333
When the network is plugged 0.014
And Tor is ready 12.549
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.754
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.189
Given I shutdown Tails and wait for the computer to power off 6.896
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.448
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.444
And the file system changes introduced in version 6.2~testoverlayfs are present 0.206
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.189
When the network is plugged 0.013
And Tor is ready 10.404
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.378
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.084
Given I shutdown Tails and wait for the computer to power off 4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.116
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.631
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.173
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.047
And Tor is ready 10.001
Then the Upgrader considers the system as up-to-date 10.474
# 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.721
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.939
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.435
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.212
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
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.018
And Tor is ready 9.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.028
After features/support/hooks.rb:339 0.734
After features/support/hooks.rb:108 0.000