Project Number Date
test_Tails_ISO_devel 4224 10 Feb 2026, 11:18

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 10:51.242 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
58.093
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
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.543
When I start Tails from USB drive "old" with network unplugged 40.263
Then the boot device has safe access rights 2.580
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 1.263
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.197
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 50.847
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 23.603
And I take note of which tps features are available 0.697
Then a Tails persistence partition exists on USB drive "old" 0.588
And I shutdown Tails and wait for the computer to power off 8.170
After features/support/hooks.rb:331 0.120
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.665
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.093
Then Tails is running from USB drive "old" 0.227
And all tps features are active 1.117
When I write some files expected to persist 1.202
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 1.656
And I take note of which tps features are available 0.275
And I shutdown Tails and wait for the computer to power off 7.906
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.633
After features/support/hooks.rb:331 0.182
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.509
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.319
And I log in to a new session 9.175
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.880
And I plug USB drive "to_upgrade" 2.264
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.948
Then the running Tails is installed on USB drive "to_upgrade" 15.631
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:331 2.301
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.261
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:0.793
Then all tps features from the old Tails version are active 0.862
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.473
And the expected persistent files created with the old Tails version are present in the filesystem 1.055
And all persistent directories from the old Tails version have safe access rights 1.776
After features/support/hooks.rb:331 1.012
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
3:30.178
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.294
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.016
And Tor is ready 13.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.128
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.011
Given I shutdown Tails and wait for the computer to power off 9.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.684
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.086
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.308
When the network is plugged 0.017
And Tor is ready 10.692
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.621
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.013
Given I shutdown Tails and wait for the computer to power off 7.913
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.901
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.092
And the file system changes introduced in version 6.3~testoverlayfs are present 0.331
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.019
And Tor is ready 10.078
Then the Upgrader considers the system as up-to-date 10.567
# 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 3.797
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.354
After features/support/hooks.rb:331 0.770
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
19.336
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.365
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.949
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.711
After features/support/hooks.rb:331 0.903
After features/support/hooks.rb:100 0.000