Project Number Date
test_Tails_ISO_21523-21524-unsafe-browser-onionshare-no-dbus-access 3 21 Apr 2026, 20:17

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:21.006 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:10.985
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 14.393
When I start Tails from USB drive "old" with network unplugged 51.699
Then the boot device has safe access rights 2.958
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:331 1.521
After features/support/hooks.rb:100 0.007
Tags: @product
1:38.015
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.136
And I start Tails from USB drive "old" with network unplugged and I login 1:1.376
Then Tails is running from USB drive "old" 0.431
And I create a persistent partition 26.149
And I take note of which tps features are available 0.862
Then a Tails persistence partition exists on USB drive "old" 0.614
And I shutdown Tails and wait for the computer to power off 8.445
After features/support/hooks.rb:331 0.430
After features/support/hooks.rb:100 0.008
Tags: @product
1:34.933
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.426
Then Tails is running from USB drive "old" 0.334
And all tps features are active 1.319
When I write some files expected to persist 1.388
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.548
And all persistent directories from the old Tails version have safe access rights 2.077
And I take note of which tps features are available 0.217
And I shutdown Tails and wait for the computer to power off 8.067
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.268
After features/support/hooks.rb:331 0.373
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.083
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.528
And I log in to a new session 14.468
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.943
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.206
Then the running Tails is installed on USB drive "to_upgrade" 17.344
And I unplug USB drive "to_upgrade" 0.171
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:331 2.341
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.855
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.680
Then all tps features from the old Tails version are active 1.664
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.375
And the expected persistent files created with the old Tails version are present in the filesystem 1.345
And all persistent directories from the old Tails version have safe access rights 2.379
After features/support/hooks.rb:331 0.949
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:55.493
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 8.739
And no SquashFS delta is installed 0.166
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.401
When the network is plugged 0.022
And Tor is ready 21.982
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.477
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.995
Given I shutdown Tails and wait for the computer to power off 21.190
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.855
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.319
And the file system changes introduced in version 6.2~testoverlayfs are present 0.261
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.212
When the network is plugged 0.016
And Tor is ready 21.488
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.404
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.753
Given I shutdown Tails and wait for the computer to power off 18.643
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.373
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.110
And the file system changes introduced in version 6.3~testoverlayfs are present 0.359
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.325
When the network is plugged 0.016
And Tor is ready 22.948
Then the Upgrader considers the system as up-to-date 0.135
# 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.641
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.605
After features/support/hooks.rb:331 1.088
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
27.639
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.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
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.054
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 18.759
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.379
After features/support/hooks.rb:331 0.790
After features/support/hooks.rb:100 0.000