Project Number Date
test_Tails_ISO_stable 6751 17 Oct 2026, 11:29

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 10:31.241 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
53.586
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.119
When I start Tails from USB drive "old" with network unplugged 36.962
Then the boot device has safe access rights 1.808
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.147
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:339 3.418
After features/support/hooks.rb:108 0.020
Tags: @product
1:18.501
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 46.470
Then Tails is running from USB drive "old" 0.190
And I create a persistent partition 22.746
And I take note of which tps features are available 6.013
Then a Tails persistence partition exists on USB drive "old" 0.463
And I shutdown Tails and wait for the computer to power off 2.539
After features/support/hooks.rb:339 0.348
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.048
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.769
Then Tails is running from USB drive "old" 0.191
And all tps features are active 6.561
When I write some files expected to persist 1.007
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.259
And all persistent directories from the old Tails version have safe access rights 1.570
And I take note of which tps features are available 5.806
And I shutdown Tails and wait for the computer to power off 2.515
# 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.119
After features/support/hooks.rb:339 0.284
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.147
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.166
And I log in to a new session 11.051
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.584
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.090
Then the running Tails is installed on USB drive "to_upgrade" 17.793
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 0.544
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.508
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.224
Then all tps features from the old Tails version are active 0.965
And Tails is running from USB drive "to_upgrade" 0.141
And the boot device has safe access rights 1.864
And the expected persistent files created with the old Tails version are present in the filesystem 0.783
And all persistent directories from the old Tails version have safe access rights 1.453
After features/support/hooks.rb:339 0.654
After features/support/hooks.rb:108 0.013
3:19.762
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.137
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
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.188
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.024
And Tor is ready 12.197
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.934
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.967
Given I shutdown Tails and wait for the computer to power off 5.237
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.175
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.295
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.188
When the network is plugged 0.033
And Tor is ready 11.132
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.334
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.352
Given I shutdown Tails and wait for the computer to power off 2.593
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.253
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.526
And the file system changes introduced in version 6.3~testoverlayfs are present 0.253
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.096
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.027
And Tor is ready 9.975
Then the Upgrader considers the system as up-to-date 0.077
# 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.046
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:339 0.504
After features/support/hooks.rb:108 0.009
17.685
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 7.837
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 8.060
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.474
After features/support/hooks.rb:339 1.033
After features/support/hooks.rb:108 0.000