Project Number Date
test_Tails_ISO_stable 6467 22 Jun 2026, 11:36

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:39.171 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:9.263
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.407
When I start Tails from USB drive "old" with network unplugged 49.621
Then the boot device has safe access rights 3.326
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:339 1.596
After features/support/hooks.rb:108 0.007
Tags: @product
1:37.238
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login 58.027
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 25.151
And I take note of which tps features are available 4.749
Then a Tails persistence partition exists on USB drive "old" 0.551
And I shutdown Tails and wait for the computer to power off 8.330
After features/support/hooks.rb:339 0.231
After features/support/hooks.rb:108 0.007
Tags: @product
1:48.946
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.993
Then Tails is running from USB drive "old" 0.252
And all tps features are active 7.124
When I write some files expected to persist 1.362
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 2.122
And I take note of which tps features are available 4.315
And I shutdown Tails and wait for the computer to power off 8.116
# 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" 13.002
After features/support/hooks.rb:339 0.430
After features/support/hooks.rb:108 0.008
Tags: @product
2:15.083
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.050
And I log in to a new session 13.850
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.941
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.198
Then the running Tails is installed on USB drive "to_upgrade" 16.439
And I unplug USB drive "to_upgrade" 0.176
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:339 2.159
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.290
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.864
Then all tps features from the old Tails version are active 1.336
And Tails is running from USB drive "to_upgrade" 0.278
And the boot device has safe access rights 2.863
And the expected persistent files created with the old Tails version are present in the filesystem 1.404
And all persistent directories from the old Tails version have safe access rights 2.456
After features/support/hooks.rb:339 1.031
After features/support/hooks.rb:108 0.034
Tags: @product @automatic_upgrade
4:8.764
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 with a persistent partition enabled and logged in 8.467
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.017
And Tor is ready 13.019
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.857
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.993
Given I shutdown Tails and wait for the computer to power off 10.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.257
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 5.667
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.161
# 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.245
When the network is plugged 0.018
And Tor is ready 9.849
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.622
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.102
Given I shutdown Tails and wait for the computer to power off 8.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.092
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 5.900
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.180
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.015
And Tor is ready 12.190
Then the Upgrader considers the system as up-to-date 10.502
# 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 4.187
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.417
After features/support/hooks.rb:339 0.716
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.584
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.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 11.126
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.010
After features/support/hooks.rb:339 0.772
After features/support/hooks.rb:108 0.000