Project Number Date
test_Tails_ISO_stable 6557 04 Aug 2026, 13:46

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:2.912 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:11.752
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.194
When I start Tails from USB drive "old" with network unplugged 55.048
Then the boot device has safe access rights 1.828
And Tails is running from USB drive "old" 0.160
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.032
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.770
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.068
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 47.328
Then Tails is running from USB drive "old" 0.270
And I create a persistent partition 21.598
And I take note of which tps features are available 5.783
Then a Tails persistence partition exists on USB drive "old" 0.469
And I shutdown Tails and wait for the computer to power off 2.544
After features/support/hooks.rb:339 0.226
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.730
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.354
Then Tails is running from USB drive "old" 0.160
And all tps features are active 6.889
When I write some files expected to persist 1.109
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.185
And all persistent directories from the old Tails version have safe access rights 1.488
And I take note of which tps features are available 5.543
And I shutdown Tails and wait for the computer to power off 2.560
# 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.193
After features/support/hooks.rb:339 0.605
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.055
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.042
And I log in to a new session 11.672
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.649
And I plug USB drive "to_upgrade" 2.171
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.325
Then the running Tails is installed on USB drive "to_upgrade" 16.948
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.762
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.803
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 57.863
Then all tps features from the old Tails version are active 1.050
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 1.992
And the expected persistent files created with the old Tails version are present in the filesystem 0.932
And all persistent directories from the old Tails version have safe access rights 1.662
After features/support/hooks.rb:339 0.937
After features/support/hooks.rb:108 0.005
3:32.760
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.088
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.163
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.305
When the network is plugged 0.028
And Tor is ready 12.187
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.029
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.061
Given I shutdown Tails and wait for the computer to power off 5.260
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.030
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.432
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.078
# 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.137
When the network is plugged 0.027
And Tor is ready 10.155
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.952
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.586
Given I shutdown Tails and wait for the computer to power off 2.536
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.233
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.058
And the file system changes introduced in version 6.3~testoverlayfs are present 0.228
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.076
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.031
And Tor is ready 10.231
Then the Upgrader considers the system as up-to-date 10.372
# 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.334
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.310
After features/support/hooks.rb:339 0.564
After features/support/hooks.rb:108 0.012
18.742
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.017
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.033
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 7.851
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.545
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.000