Project Number Date
test_Tails_ISO_post-rm-7.11 8 20 Aug 2026, 23:50

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:25.812 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:24.174
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.109
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.037
And I write an old version of the Tails USB image to disk "old" 13.717
When I start Tails from USB drive "old" with network unplugged 1:6.141
Then the boot device has safe access rights 2.488
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.404
After features/support/hooks.rb:108 0.026
Tags: @product
1:20.219
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 47.762
Then Tails is running from USB drive "old" 0.189
And I create a persistent partition 22.760
And I take note of which tps features are available 6.389
Then a Tails persistence partition exists on USB drive "old" 0.475
And I shutdown Tails and wait for the computer to power off 2.542
After features/support/hooks.rb:339 0.627
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.931
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.393
Then Tails is running from USB drive "old" 0.265
And all tps features are active 7.688
When I write some files expected to persist 1.289
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.140
And all persistence configuration files have safe access rights 0.289
And all persistent directories from the old Tails version have safe access rights 1.631
And I take note of which tps features are available 6.045
And I shutdown Tails and wait for the computer to power off 2.510
# 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.598
After features/support/hooks.rb:339 0.339
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.249
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 without a persistent partition and stopped at Tails Greeter's login screen 8.451
And I log in to a new session 11.155
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.667
And I plug USB drive "to_upgrade" 2.180
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.814
Then the running Tails is installed on USB drive "to_upgrade" 17.731
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 2.083
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.919
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.506
Then all tps features from the old Tails version are active 1.120
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.191
And the expected persistent files created with the old Tails version are present in the filesystem 0.991
And all persistent directories from the old Tails version have safe access rights 1.806
After features/support/hooks.rb:339 0.721
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:31.194
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.072
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.339
When the network is plugged 0.040
And Tor is ready 11.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.886
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.235
Given I shutdown Tails and wait for the computer to power off 5.357
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.338
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 7.939
And the file system changes introduced in version 6.2~testoverlayfs are present 0.197
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.149
When the network is plugged 0.026
And Tor is ready 9.583
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.525
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.520
Given I shutdown Tails and wait for the computer to power off 2.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.895
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.922
And the file system changes introduced in version 6.3~testoverlayfs are present 0.425
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.169
When the network is plugged 0.033
And Tor is ready 10.444
Then the Upgrader considers the system as up-to-date 0.108
# 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.681
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:339 0.599
After features/support/hooks.rb:108 0.049
Tags: @product @automatic_upgrade
19.123
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.041
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 8.955
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.715
After features/support/hooks.rb:339 0.646
After features/support/hooks.rb:108 0.000