Project Number Date
test_Tails_ISO_stable 6556 04 Aug 2026, 13:55

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:42.450 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:0.214
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.245
When I start Tails from USB drive "old" with network unplugged 42.154
Then the boot device has safe access rights 2.074
And Tails is running from USB drive "old" 0.216
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 3.905
After features/support/hooks.rb:108 0.021
Tags: @product
1:24.947
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.130
And I start Tails from USB drive "old" with network unplugged and I login 49.249
Then Tails is running from USB drive "old" 0.213
And I create a persistent partition 24.688
And I take note of which tps features are available 7.405
Then a Tails persistence partition exists on USB drive "old" 0.579
And I shutdown Tails and wait for the computer to power off 2.679
After features/support/hooks.rb:339 0.422
After features/support/hooks.rb:108 0.008
Tags: @product
1:35.127
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.149
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.182
Then Tails is running from USB drive "old" 0.205
And all tps features are active 6.874
When I write some files expected to persist 1.084
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.817
And I take note of which tps features are available 6.794
And I shutdown Tails and wait for the computer to power off 2.567
# 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.044
After features/support/hooks.rb:339 0.194
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.624
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 without a persistent partition and stopped at Tails Greeter's login screen 8.882
And I log in to a new session 13.551
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.995
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.847
Then the running Tails is installed on USB drive "to_upgrade" 17.874
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.720
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.927
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.927
Then all tps features from the old Tails version are active 1.525
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.023
And all persistent directories from the old Tails version have safe access rights 1.690
After features/support/hooks.rb:339 0.757
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:44.709
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.608
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.026
And Tor is ready 12.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.318
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.134
Given I shutdown Tails and wait for the computer to power off 5.677
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.858
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 7.845
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.097
# 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.193
When the network is plugged 0.069
And Tor is ready 10.471
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.744
Given I shutdown Tails and wait for the computer to power off 2.598
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.339
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.477
And the file system changes introduced in version 6.3~testoverlayfs are present 0.301
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.032
And Tor is ready 10.259
Then the Upgrader considers the system as up-to-date 10.463
# 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.426
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.296
After features/support/hooks.rb:339 0.603
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
33.900
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 21.353
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.036
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 9.972
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.237
After features/support/hooks.rb:339 0.839
After features/support/hooks.rb:108 0.000