Project Number Date
test_Tails_ISO_post-7.14-release-process 1 29 Sep 2026, 20:26

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:59.152 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:21.224
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.110
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.566
When I start Tails from USB drive "old" with network unplugged 1:3.302
Then the boot device has safe access rights 2.458
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.237
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 3.864
After features/support/hooks.rb:108 0.035
Tags: @product
1:26.433
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login 51.297
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 25.014
And I take note of which tps features are available 6.546
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 2.680
After features/support/hooks.rb:339 0.422
After features/support/hooks.rb:108 0.007
Tags: @product
1:38.431
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.213
Then Tails is running from USB drive "old" 0.201
And all tps features are active 7.649
When I write some files expected to persist 1.346
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.260
And all persistent directories from the old Tails version have safe access rights 1.862
And I take note of which tps features are available 6.261
And I shutdown Tails and wait for the computer to power off 4.107
# 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.268
After features/support/hooks.rb:339 0.384
After features/support/hooks.rb:108 0.008
Tags: @product
2:17.141
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.744
And I log in to a new session 12.980
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.898
And I plug USB drive "to_upgrade" 2.265
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.740
Then the running Tails is installed on USB drive "to_upgrade" 20.268
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.117
After features/support/hooks.rb:339 0.620
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.259
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.409
Then all tps features from the old Tails version are active 1.104
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 2.518
And the expected persistent files created with the old Tails version are present in the filesystem 1.164
And all persistent directories from the old Tails version have safe access rights 1.769
After features/support/hooks.rb:339 0.992
After features/support/hooks.rb:108 0.056
Tags: @product @automatic_upgrade
3:45.703
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.754
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.300
When the network is plugged 0.033
And Tor is ready 13.243
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.024
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.930
Given I shutdown Tails and wait for the computer to power off 5.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.694
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 8.386
And the file system changes introduced in version 6.2~testoverlayfs are present 0.189
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.172
When the network is plugged 0.026
And Tor is ready 10.838
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.361
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.802
Given I shutdown Tails and wait for the computer to power off 4.217
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.256
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.123
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.047
# 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.097
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.154
When the network is plugged 0.030
And Tor is ready 10.487
Then the Upgrader considers the system as up-to-date 0.095
# 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.608
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.691
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
19.957
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.410
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 8.888
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.345
After features/support/hooks.rb:339 0.762
After features/support/hooks.rb:108 0.000