Project Number Date
test_Tails_ISO_stable 6055 13 Jan 2026, 11:42

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:11.644 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.145
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 12.834
When I start Tails from USB drive "old" with network unplugged 48.906
Then the boot device has safe access rights 2.651
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:331 3.430
After features/support/hooks.rb:100 0.012
Tags: @product
1:33.680
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 51.876
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 23.093
And I take note of which tps features are available 0.725
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 17.134
After features/support/hooks.rb:331 0.193
After features/support/hooks.rb:100 0.006
Tags: @product
1:20.266
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.420
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.114
When I write some files expected to persist 1.172
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.363
And all persistent directories from the old Tails version have safe access rights 1.759
And I take note of which tps features are available 0.144
And I shutdown Tails and wait for the computer to power off 4.053
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.725
After features/support/hooks.rb:331 0.562
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.720
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.344
And I log in to a new session 13.215
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.792
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.221
Then the running Tails is installed on USB drive "to_upgrade" 14.660
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:331 6.986
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.164
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.417
Then all tps features from the old Tails version are active 0.999
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.483
And the expected persistent files created with the old Tails version are present in the filesystem 1.107
And all persistent directories from the old Tails version have safe access rights 1.861
After features/support/hooks.rb:331 0.519
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:33.813
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.937
And no SquashFS delta is installed 0.058
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.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.016
And Tor is ready 13.147
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.747
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 9.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.738
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.122
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.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.122
# 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.178
When the network is plugged 0.017
And Tor is ready 11.731
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.672
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.295
Given I shutdown Tails and wait for the computer to power off 7.888
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.070
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.221
And the file system changes introduced in version 6.3~testoverlayfs are present 0.314
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.199
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.237
When the network is plugged 0.041
And Tor is ready 10.999
Then the Upgrader considers the system as up-to-date 10.493
# 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.188
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:331 1.134
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
20.853
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.775
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.699
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.041
After features/support/hooks.rb:331 0.900
After features/support/hooks.rb:100 0.000