Project Number Date
test_Tails_ISO_stable 6397 22 May 2026, 07:32

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:39.932 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:9.937
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.255
When I start Tails from USB drive "old" with network unplugged 52.076
Then the boot device has safe access rights 2.821
And Tails is running from USB drive "old" 0.236
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:335 1.249
After features/support/hooks.rb:104 0.007
Tags: @product
1:28.649
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 54.119
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 24.675
And I take note of which tps features are available 0.342
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 8.537
After features/support/hooks.rb:335 0.309
After features/support/hooks.rb:104 0.009
Tags: @product
1:29.086
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.399
Then Tails is running from USB drive "old" 0.258
And all tps features are active 1.318
When I write some files expected to persist 1.400
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.087
And I take note of which tps features are available 0.154
And I shutdown Tails and wait for the computer to power off 8.120
# 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.673
After features/support/hooks.rb:335 0.267
After features/support/hooks.rb:104 0.007
Tags: @product
2:11.795
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.195
And I log in to a new session 12.455
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.783
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.034
Then the running Tails is installed on USB drive "to_upgrade" 15.767
And I unplug USB drive "to_upgrade" 0.182
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:335 1.990
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.717
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
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.995
Then all tps features from the old Tails version are active 1.043
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.828
And the expected persistent files created with the old Tails version are present in the filesystem 1.369
And all persistent directories from the old Tails version have safe access rights 2.161
After features/support/hooks.rb:335 0.936
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
3:46.756
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.684
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.016
And Tor is ready 13.711
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.961
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.638
Given I shutdown Tails and wait for the computer to power off 9.649
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.506
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.210
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.190
When the network is plugged 0.016
And Tor is ready 11.563
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.940
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.913
Given I shutdown Tails and wait for the computer to power off 8.112
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.283
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.360
And the file system changes introduced in version 6.3~testoverlayfs are present 0.385
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.017
And Tor is ready 9.939
Then the Upgrader considers the system as up-to-date 10.581
# 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.805
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:335 0.772
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
19.989
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.673
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
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.016
And Tor is ready 10.044
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.864
After features/support/hooks.rb:335 0.794
After features/support/hooks.rb:104 0.000