Project Number Date
test_Tails_ISO_web-release-7.14 1 29 Sep 2026, 17:46

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:10.666 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:22.545
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.112
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.804
When I start Tails from USB drive "old" with network unplugged 1:4.262
Then the boot device has safe access rights 2.665
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 1.102
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.534
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 "old" with network unplugged and I login 50.031
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 25.423
And I take note of which tps features are available 7.022
Then a Tails persistence partition exists on USB drive "old" 0.538
And I shutdown Tails and wait for the computer to power off 4.059
After features/support/hooks.rb:339 0.354
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.297
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.875
Then Tails is running from USB drive "old" 0.215
And all tps features are active 7.678
When I write some files expected to persist 1.183
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.275
And all persistent directories from the old Tails version have safe access rights 1.854
And I take note of which tps features are available 6.201
And I shutdown Tails and wait for the computer to power off 4.024
# 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.747
After features/support/hooks.rb:339 0.519
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.013
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.518
And I log in to a new session 10.978
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.683
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.069
Then the running Tails is installed on USB drive "to_upgrade" 19.104
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 1.831
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.182
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.478
Then all tps features from the old Tails version are active 1.494
And Tails is running from USB drive "to_upgrade" 0.454
And the boot device has safe access rights 2.584
And the expected persistent files created with the old Tails version are present in the filesystem 1.085
And all persistent directories from the old Tails version have safe access rights 1.977
After features/support/hooks.rb:339 0.559
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:54.175
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 9.123
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.323
When the network is plugged 0.042
And Tor is ready 13.785
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.302
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.074
Given I shutdown Tails and wait for the computer to power off 5.427
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.582
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.302
And the file system changes introduced in version 6.2~testoverlayfs are present 0.179
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.198
When the network is plugged 0.029
And Tor is ready 10.434
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.323
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.685
Given I shutdown Tails and wait for the computer to power off 3.963
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.094
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 9.828
And the file system changes introduced in version 6.3~testoverlayfs are present 0.339
And only the 6.3~testoverlayfs SquashFS delta is installed 0.033
# 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.105
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.038
And Tor is ready 10.116
Then the Upgrader considers the system as up-to-date 10.473
# 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.879
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.426
After features/support/hooks.rb:339 0.835
After features/support/hooks.rb:108 0.049
Tags: @product @automatic_upgrade
19.917
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.366
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.046
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 10.102
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.079
After features/support/hooks.rb:339 0.790
After features/support/hooks.rb:108 0.000