Project Number Date
test_Tails_ISO_21523-21524-unsafe-browser-onionshare-no-dbus-access 4 22 Apr 2026, 18:42

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:57.627 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:24.009
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.499
When I start Tails from USB drive "old" with network unplugged 1:5.875
Then the boot device has safe access rights 2.888
And Tails is running from USB drive "old" 0.249
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.170
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 1.381
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.130
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 57.565
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 23.170
And I take note of which tps features are available 0.686
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 7.858
After features/support/hooks.rb:331 0.268
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.774
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.286
Then Tails is running from USB drive "old" 0.214
And all tps features are active 1.321
When I write some files expected to persist 1.234
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.523
And all persistent directories from the old Tails version have safe access rights 1.813
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 7.854
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.156
After features/support/hooks.rb:331 0.607
After features/support/hooks.rb:100 0.007
Tags: @product
2:19.470
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.031
And I log in to a new session 17.339
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.775
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.570
Then the running Tails is installed on USB drive "to_upgrade" 16.224
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 3.662
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.784
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.175
Then all tps features from the old Tails version are active 0.929
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 2.397
And the expected persistent files created with the old Tails version are present in the filesystem 1.118
And all persistent directories from the old Tails version have safe access rights 1.860
After features/support/hooks.rb:331 0.984
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
4:36.497
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 9.017
And no SquashFS delta is installed 0.184
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.024
And Tor is ready 25.444
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.572
Given I shutdown Tails and wait for the computer to power off 22.142
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.404
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.122
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# 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.204
When the network is plugged 0.014
And Tor is ready 21.116
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.355
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.410
Given I shutdown Tails and wait for the computer to power off 13.125
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.305
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.064
And the file system changes introduced in version 6.3~testoverlayfs are present 0.347
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.016
And Tor is ready 21.834
Then the Upgrader considers the system as up-to-date 0.097
# 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.300
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.345
After features/support/hooks.rb:331 1.097
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
27.959
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.821
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 19.340
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.364
After features/support/hooks.rb:331 0.773
After features/support/hooks.rb:100 0.000