Project Number Date
test_Tails_ISO_devel 4246 23 Feb 2026, 12:10

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 13:23.829 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:11.339
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 14.648
When I start Tails from USB drive "old" with network unplugged 51.624
Then the boot device has safe access rights 3.091
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.158
After features/support/hooks.rb:331 1.338
After features/support/hooks.rb:100 0.009
Tags: @product
1:36.209
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 57.781
Then Tails is running from USB drive "old" 0.253
And I create a persistent partition 28.120
And I take note of which tps features are available 0.859
Then a Tails persistence partition exists on USB drive "old" 0.686
And I shutdown Tails and wait for the computer to power off 8.427
After features/support/hooks.rb:331 0.203
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.496
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.474
Then Tails is running from USB drive "old" 0.253
And all tps features are active 1.181
When I write some files expected to persist 1.432
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 2.534
And I take note of which tps features are available 0.256
And I shutdown Tails and wait for the computer to power off 8.554
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.185
After features/support/hooks.rb:331 0.419
After features/support/hooks.rb:100 0.013
Tags: @product
2:18.866
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.912
And I log in to a new session 16.160
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.076
And I plug USB drive "to_upgrade" 2.264
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.251
Then the running Tails is installed on USB drive "to_upgrade" 16.857
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:331 3.908
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.115
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.293
Then all tps features from the old Tails version are active 1.134
And Tails is running from USB drive "to_upgrade" 0.284
And the boot device has safe access rights 3.211
And the expected persistent files created with the old Tails version are present in the filesystem 1.469
And all persistent directories from the old Tails version have safe access rights 2.360
After features/support/hooks.rb:331 0.971
After features/support/hooks.rb:100 0.009
4:56.867
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 8.889
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.420
When the network is plugged 0.020
And Tor is ready 23.796
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.570
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.581
Given I shutdown Tails and wait for the computer to power off 21.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.419
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.359
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.225
When the network is plugged 0.015
And Tor is ready 22.318
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.382
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.745
Given I shutdown Tails and wait for the computer to power off 17.973
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.336
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.175
And the file system changes introduced in version 6.3~testoverlayfs are present 0.414
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.016
And Tor is ready 20.809
Then the Upgrader considers the system as up-to-date 0.136
# 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.506
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.594
After features/support/hooks.rb:331 0.840
After features/support/hooks.rb:100 0.012
29.179
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.703
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.068
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.018
And Tor is ready 20.723
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.382
After features/support/hooks.rb:331 0.575
After features/support/hooks.rb:100 0.000