Project Number Date
test_Tails_ISO_stable 6654 10 Sep 2026, 07: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 11:22.115 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:7.677
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.599
When I start Tails from USB drive "old" with network unplugged 50.253
Then the boot device has safe access rights 2.062
And Tails is running from USB drive "old" 0.205
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.438
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.534
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 48.802
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 23.150
And I take note of which tps features are available 6.916
Then a Tails persistence partition exists on USB drive "old" 0.544
And I shutdown Tails and wait for the computer to power off 3.792
After features/support/hooks.rb:339 0.288
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.988
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.083
Then Tails is running from USB drive "old" 0.227
And all tps features are active 7.247
When I write some files expected to persist 1.054
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.111
And all persistence configuration files have safe access rights 0.201
And all persistent directories from the old Tails version have safe access rights 1.605
And I take note of which tps features are available 6.097
And I shutdown Tails and wait for the computer to power off 2.524
# 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.749
After features/support/hooks.rb:339 0.344
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.384
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.186
And I log in to a new session 11.961
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.926
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.544
Then the running Tails is installed on USB drive "to_upgrade" 18.269
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 1.749
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.691
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.808
Then all tps features from the old Tails version are active 1.180
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.040
And the expected persistent files created with the old Tails version are present in the filesystem 0.861
And all persistent directories from the old Tails version have safe access rights 1.480
After features/support/hooks.rb:339 0.502
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:36.362
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 7.903
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.405
When the network is plugged 0.039
And Tor is ready 11.681
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.414
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.121
Given I shutdown Tails and wait for the computer to power off 5.515
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.658
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.600
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.213
When the network is plugged 0.029
And Tor is ready 10.408
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.305
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.350
Given I shutdown Tails and wait for the computer to power off 2.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.208
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.104
And the file system changes introduced in version 6.3~testoverlayfs are present 0.296
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.105
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160
When the network is plugged 0.035
And Tor is ready 10.185
Then the Upgrader considers the system as up-to-date 10.459
# 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.159
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.340
After features/support/hooks.rb:339 0.957
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
18.474
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.653
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.021
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 8.554
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.956
After features/support/hooks.rb:339 0.691
After features/support/hooks.rb:108 0.000