Project Number Date
test_Tails_ISO_stable 6088 23 Jan 2026, 12:06

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:17.513 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:34.082
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.034
And I plug USB drive "old" 1.038
And I write an old version of the Tails USB image to disk "old" 13.975
When I start Tails from USB drive "old" with network unplugged 1:14.868
Then the boot device has safe access rights 3.214
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:331 3.694
After features/support/hooks.rb:100 0.027
Tags: @product
1:28.862
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.130
And I start Tails from USB drive "old" with network unplugged and I login 55.718
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 24.422
And I take note of which tps features are available 0.812
Then a Tails persistence partition exists on USB drive "old" 0.724
And I shutdown Tails and wait for the computer to power off 6.733
After features/support/hooks.rb:331 0.151
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.523
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.067
Then Tails is running from USB drive "old" 0.260
And all tps features are active 1.138
When I write some files expected to persist 1.323
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.266
And all persistent directories from the old Tails version have safe access rights 2.099
And I take note of which tps features are available 0.268
And I shutdown Tails and wait for the computer to power off 4.216
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.600
After features/support/hooks.rb:331 0.306
After features/support/hooks.rb:100 0.007
Tags: @product
2:19.604
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.466
And I log in to a new session 13.634
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.325
And I plug USB drive "to_upgrade" 2.292
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.764
Then the running Tails is installed on USB drive "to_upgrade" 15.824
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:331 2.240
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.885
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.859
Then all tps features from the old Tails version are active 1.007
And Tails is running from USB drive "to_upgrade" 0.273
And the boot device has safe access rights 2.664
And the expected persistent files created with the old Tails version are present in the filesystem 1.183
And all persistent directories from the old Tails version have safe access rights 1.815
After features/support/hooks.rb:331 0.973
After features/support/hooks.rb:100 0.006
3:57.937
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 9.056
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.258
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.339
When the network is plugged 0.019
And Tor is ready 14.642
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.035
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.503
Given I shutdown Tails and wait for the computer to power off 15.133
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.900
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.144
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.204
When the network is plugged 0.014
And Tor is ready 10.026
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.426
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.079
Given I shutdown Tails and wait for the computer to power off 7.898
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.591
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 1.140
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.047
# 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.178
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.015
And Tor is ready 11.674
Then the Upgrader considers the system as up-to-date 10.600
# 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.148
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.349
After features/support/hooks.rb:331 1.077
After features/support/hooks.rb:100 0.013
20.617
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.543
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.148
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 10.159
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.333
After features/support/hooks.rb:331 0.587
After features/support/hooks.rb:100 0.000