Project Number Date
test_Tails_ISO_stable 6709 30 Sep 2026, 11:38

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:28.838 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:1.419
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.110
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.862
When I start Tails from USB drive "old" with network unplugged 43.527
Then the boot device has safe access rights 2.234
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.817
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.854
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 49.062
Then Tails is running from USB drive "old" 0.219
And I create a persistent partition 24.140
And I take note of which tps features are available 6.643
Then a Tails persistence partition exists on USB drive "old" 0.594
And I shutdown Tails and wait for the computer to power off 4.111
After features/support/hooks.rb:339 0.478
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.547
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.732
Then Tails is running from USB drive "old" 0.244
And all tps features are active 7.347
When I write some files expected to persist 1.068
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.245
And all persistent directories from the old Tails version have safe access rights 1.943
And I take note of which tps features are available 6.488
And I shutdown Tails and wait for the computer to power off 4.056
# 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.142
After features/support/hooks.rb:339 0.303
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.873
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 without a persistent partition and stopped at Tails Greeter's login screen 8.523
And I log in to a new session 11.784
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.806
And I plug USB drive "to_upgrade" 2.257
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.855
Then the running Tails is installed on USB drive "to_upgrade" 19.389
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 3.744
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.169
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.127
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.414
Then all tps features from the old Tails version are active 1.100
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.475
And the expected persistent files created with the old Tails version are present in the filesystem 1.034
And all persistent directories from the old Tails version have safe access rights 1.803
After features/support/hooks.rb:339 0.528
After features/support/hooks.rb:108 0.043
Tags: @product @automatic_upgrade
3:40.747
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 8.397
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.026
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.384
When the network is plugged 0.032
And Tor is ready 12.133
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.851
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.267
Given I shutdown Tails and wait for the computer to power off 5.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.642
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.271
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.108
# 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.175
When the network is plugged 0.026
And Tor is ready 10.586
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.942
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.154
Given I shutdown Tails and wait for the computer to power off 3.915
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.743
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.756
And the file system changes introduced in version 6.3~testoverlayfs are present 0.392
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.026
And Tor is ready 10.343
Then the Upgrader considers the system as up-to-date 0.085
# 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.520
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.404
After features/support/hooks.rb:339 0.704
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
19.226
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 8.418
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 10.154
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.313
After features/support/hooks.rb:339 0.962
After features/support/hooks.rb:108 0.000