Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 79 01 Jul 2026, 04:30

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 11:40.883 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:8.761
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.044
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.039
When I start Tails from USB drive "old" with network unplugged 51.373
Then the boot device has safe access rights 2.652
And Tails is running from USB drive "old" 0.200
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 1.401
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.246
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 52.684
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 23.993
And I take note of which tps features are available 3.893
Then a Tails persistence partition exists on USB drive "old" 0.485
And I shutdown Tails and wait for the computer to power off 7.891
After features/support/hooks.rb:339 0.163
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.604
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.888
Then Tails is running from USB drive "old" 0.236
And all tps features are active 4.689
When I write some files expected to persist 1.349
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.289
And all persistent directories from the old Tails version have safe access rights 1.826
And I take note of which tps features are available 3.624
And I shutdown Tails and wait for the computer to power off 7.944
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.555
After features/support/hooks.rb:339 0.221
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.776
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.013
And I log in to a new session 11.968
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.733
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.259
Then the running Tails is installed on USB drive "to_upgrade" 14.269
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 2.258
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.428
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.754
Then all tps features from the old Tails version are active 0.944
And Tails is running from USB drive "to_upgrade" 0.206
And the boot device has safe access rights 2.398
And the expected persistent files created with the old Tails version are present in the filesystem 1.126
And all persistent directories from the old Tails version have safe access rights 1.920
After features/support/hooks.rb:339 0.806
After features/support/hooks.rb:108 0.005
3:48.610
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.835
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.314
When the network is plugged 0.017
And Tor is ready 13.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.823
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.405
Given I shutdown Tails and wait for the computer to power off 9.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.450
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.736
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.017
And Tor is ready 10.987
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.538
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.018
Given I shutdown Tails and wait for the computer to power off 7.945
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.859
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 4.826
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.043
And Tor is ready 9.590
Then the Upgrader considers the system as up-to-date 10.506
# 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.184
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.400
After features/support/hooks.rb:339 0.833
After features/support/hooks.rb:108 0.010
20.456
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.419
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.531
After features/support/hooks.rb:339 0.760
After features/support/hooks.rb:108 0.000