Project Number Date
test_Tails_ISO_21523-21524-unsafe-browser-onionshare-no-dbus-access 8 29 Apr 2026, 18:20

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:17.204 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:21.294
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.077
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" 14.181
When I start Tails from USB drive "old" with network unplugged 1:1.939
Then the boot device has safe access rights 3.306
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:331 4.066
After features/support/hooks.rb:100 0.008
Tags: @product
1:33.959
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 58.901
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 25.036
And I take note of which tps features are available 0.910
Then a Tails persistence partition exists on USB drive "old" 0.572
And I shutdown Tails and wait for the computer to power off 8.219
After features/support/hooks.rb:331 0.466
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.035
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.776
Then Tails is running from USB drive "old" 0.291
And all tps features are active 1.242
When I write some files expected to persist 1.485
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.513
And all persistent directories from the old Tails version have safe access rights 2.173
And I take note of which tps features are available 0.174
And I shutdown Tails and wait for the computer to power off 7.186
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.902
After features/support/hooks.rb:331 0.367
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.112
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 9.060
And I log in to a new session 13.897
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.948
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.330
Then the running Tails is installed on USB drive "to_upgrade" 17.334
And I unplug USB drive "to_upgrade" 0.151
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:331 2.230
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.087
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.415
Then all tps features from the old Tails version are active 1.156
And Tails is running from USB drive "to_upgrade" 0.289
And the boot device has safe access rights 2.828
And the expected persistent files created with the old Tails version are present in the filesystem 1.287
And all persistent directories from the old Tails version have safe access rights 2.012
After features/support/hooks.rb:331 0.633
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:52.095
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.649
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.398
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.018
And Tor is ready 21.622
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.455
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.419
Given I shutdown Tails and wait for the computer to power off 20.677
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.263
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 1.444
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.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.203
When the network is plugged 0.022
And Tor is ready 21.101
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.364
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.393
Given I shutdown Tails and wait for the computer to power off 17.858
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.260
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.166
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.016
And Tor is ready 22.445
Then the Upgrader considers the system as up-to-date 0.125
# 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.602
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.504
After features/support/hooks.rb:331 1.028
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
27.620
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.012
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
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.051
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 18.887
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.364
After features/support/hooks.rb:331 0.630
After features/support/hooks.rb:100 0.000