Project Number Date
test_Tails_ISO_stable 6554 04 Aug 2026, 00:51

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:0.159 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:4.980
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.172
When I start Tails from USB drive "old" with network unplugged 48.381
Then the boot device has safe access rights 1.855
And Tails is running from USB drive "old" 0.135
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.132
And I unplug USB drive "old" 0.103
After features/support/hooks.rb:339 3.555
After features/support/hooks.rb:108 0.012
Tags: @product
1:17.732
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.223
Then Tails is running from USB drive "old" 0.191
And I create a persistent partition 22.281
And I take note of which tps features are available 5.967
Then a Tails persistence partition exists on USB drive "old" 0.464
And I shutdown Tails and wait for the computer to power off 2.526
After features/support/hooks.rb:339 0.656
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.935
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.091
Then Tails is running from USB drive "old" 0.170
And all tps features are active 6.643
When I write some files expected to persist 1.088
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.134
And all persistence configuration files have safe access rights 0.215
And all persistent directories from the old Tails version have safe access rights 1.676
And I take note of which tps features are available 5.643
And I shutdown Tails and wait for the computer to power off 5.027
# 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.165
After features/support/hooks.rb:339 0.396
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.689
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.250
And I log in to a new session 11.928
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.639
And I plug USB drive "to_upgrade" 2.260
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.440
Then the running Tails is installed on USB drive "to_upgrade" 16.940
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 0.708
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.267
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.651
Then all tps features from the old Tails version are active 0.956
And Tails is running from USB drive "to_upgrade" 0.149
And the boot device has safe access rights 2.049
And the expected persistent files created with the old Tails version are present in the filesystem 0.985
And all persistent directories from the old Tails version have safe access rights 1.398
After features/support/hooks.rb:339 0.961
After features/support/hooks.rb:108 0.005
3:33.279
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 20.960
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.296
When the network is plugged 0.029
And Tor is ready 12.403
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.974
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.259
Given I shutdown Tails and wait for the computer to power off 5.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.074
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.157
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.081
# 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.139
When the network is plugged 0.034
And Tor is ready 10.127
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.358
Given I shutdown Tails and wait for the computer to power off 2.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.978
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.207
And the file system changes introduced in version 6.3~testoverlayfs are present 0.332
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.095
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.023
And Tor is ready 10.063
Then the Upgrader considers the system as up-to-date 0.132
# 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 2.965
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.301
After features/support/hooks.rb:339 0.547
After features/support/hooks.rb:108 0.012
19.275
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.652
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 9.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.424
After features/support/hooks.rb:339 0.897
After features/support/hooks.rb:108 0.000