Project Number Date
test_Tails_ISO_devel 4259 28 Feb 2026, 11:57

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 12:59.597 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.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.324
When I start Tails from USB drive "old" with network unplugged 47.313
Then the boot device has safe access rights 3.233
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.158
After features/support/hooks.rb:331 1.302
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 54.895
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 24.795
And I take note of which tps features are available 0.751
Then a Tails persistence partition exists on USB drive "old" 0.501
And I shutdown Tails and wait for the computer to power off 6.837
After features/support/hooks.rb:331 0.222
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.675
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.958
Then Tails is running from USB drive "old" 0.221
And all tps features are active 1.228
When I write some files expected to persist 1.426
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 2.023
And I take note of which tps features are available 0.185
And I shutdown Tails and wait for the computer to power off 8.276
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.656
After features/support/hooks.rb:331 0.260
After features/support/hooks.rb:100 0.007
Tags: @product
2:15.678
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.311
And I log in to a new session 13.931
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.834
And I plug USB drive "to_upgrade" 2.282
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.300
Then the running Tails is installed on USB drive "to_upgrade" 16.672
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:331 3.815
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.301
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.048
Then all tps features from the old Tails version are active 0.984
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.718
And the expected persistent files created with the old Tails version are present in the filesystem 1.250
And all persistent directories from the old Tails version have safe access rights 1.980
After features/support/hooks.rb:331 0.942
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
5:0.612
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.564
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
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.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.015
And Tor is ready 25.041
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.438
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.832
Given I shutdown Tails and wait for the computer to power off 19.870
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.423
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.154
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
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.131
# 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.192
When the network is plugged 0.018
And Tor is ready 21.457
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.389
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.391
Given I shutdown Tails and wait for the computer to power off 17.793
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.850
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.160
And the file system changes introduced in version 6.3~testoverlayfs are present 0.427
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.018
And Tor is ready 39.550
Then the Upgrader considers the system as up-to-date 0.096
# 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.583
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.410
After features/support/hooks.rb:331 0.859
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
27.475
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.627
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 18.986
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.417
After features/support/hooks.rb:331 0.878
After features/support/hooks.rb:100 0.000