Project Number Date
test_Tails_ISO_stable 6531 26 Jul 2026, 11:39

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:51.848 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:6.732
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.363
When I start Tails from USB drive "old" with network unplugged 48.992
Then the boot device has safe access rights 2.638
And Tails is running from USB drive "old" 0.213
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:339 1.110
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.626
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 54.405
Then Tails is running from USB drive "old" 0.242
And I create a persistent partition 24.196
And I take note of which tps features are available 4.136
Then a Tails persistence partition exists on USB drive "old" 0.538
And I shutdown Tails and wait for the computer to power off 4.058
After features/support/hooks.rb:339 0.243
After features/support/hooks.rb:108 0.008
Tags: @product
1:37.515
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.301
Then Tails is running from USB drive "old" 0.319
And all tps features are active 4.707
When I write some files expected to persist 1.332
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.024
And I take note of which tps features are available 5.206
And I shutdown Tails and wait for the computer to power off 4.087
# 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.938
After features/support/hooks.rb:339 0.343
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.143
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.097
And I log in to a new session 13.793
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.722
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.045
Then the running Tails is installed on USB drive "to_upgrade" 15.981
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.054
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.581
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.384
Then all tps features from the old Tails version are active 1.182
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.517
And the expected persistent files created with the old Tails version are present in the filesystem 1.300
And all persistent directories from the old Tails version have safe access rights 1.854
After features/support/hooks.rb:339 0.639
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:52.817
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.953
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
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.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.356
When the network is plugged 0.013
And Tor is ready 12.639
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.417
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.409
Given I shutdown Tails and wait for the computer to power off 6.954
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.397
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.263
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.236
When the network is plugged 0.034
And Tor is ready 11.613
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.500
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.529
Given I shutdown Tails and wait for the computer to power off 4.386
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.952
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.683
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.015
And Tor is ready 10.221
Then the Upgrader considers the system as up-to-date 10.536
# 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 4.459
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.413
After features/support/hooks.rb:339 0.671
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.431
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.678
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 11.488
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.899
After features/support/hooks.rb:339 0.857
After features/support/hooks.rb:108 0.000