Project Number Date
test_Tails_ISO_devel 4245 22 Feb 2026, 12:19

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 14:15.780 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:22.078
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 29.785
When I start Tails from USB drive "old" with network unplugged 47.132
Then the boot device has safe access rights 2.995
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.240
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:331 1.234
After features/support/hooks.rb:100 0.011
Tags: @product
1:37.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:0.472
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 27.236
And I take note of which tps features are available 1.241
Then a Tails persistence partition exists on USB drive "old" 0.769
And I shutdown Tails and wait for the computer to power off 7.486
After features/support/hooks.rb:331 0.296
After features/support/hooks.rb:100 0.012
Tags: @product
1:45.788
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:13.734
Then Tails is running from USB drive "old" 0.282
And all tps features are active 1.672
When I write some files expected to persist 1.392
# 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.331
And all persistent directories from the old Tails version have safe access rights 2.217
And I take note of which tps features are available 0.436
And I shutdown Tails and wait for the computer to power off 7.512
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.813
After features/support/hooks.rb:331 0.211
After features/support/hooks.rb:100 0.012
Tags: @product
2:29.488
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.662
And I log in to a new session 12.720
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.311
And I plug USB drive "to_upgrade" 2.952
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.009
Then the running Tails is installed on USB drive "to_upgrade" 19.409
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:331 2.502
After features/support/hooks.rb:100 0.000
Tags: @product
1:23.062
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.708
Then all tps features from the old Tails version are active 1.714
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 2.812
And the expected persistent files created with the old Tails version are present in the filesystem 1.249
And all persistent directories from the old Tails version have safe access rights 2.122
After features/support/hooks.rb:331 0.818
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:7.292
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.442
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.420
When the network is plugged 0.060
And Tor is ready 23.173
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.578
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.433
Given I shutdown Tails and wait for the computer to power off 23.010
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.257
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.013
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.262
When the network is plugged 0.053
And Tor is ready 22.120
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.560
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.245
Given I shutdown Tails and wait for the computer to power off 17.960
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.592
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.974
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.092
And Tor is ready 22.920
Then the Upgrader considers the system as up-to-date 0.110
# 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 5.351
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.474
After features/support/hooks.rb:331 0.865
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
30.331
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.977
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 19.327
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.556
After features/support/hooks.rb:331 1.164
After features/support/hooks.rb:100 0.000