Project Number Date
test_Tails_ISO_21523-21524-unsafe-browser-onionshare-no-dbus-access 9 30 Apr 2026, 18:21

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:11.449 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:14.470
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.354
When I start Tails from USB drive "old" with network unplugged 56.861
Then the boot device has safe access rights 2.534
And Tails is running from USB drive "old" 0.187
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 3.648
After features/support/hooks.rb:100 0.040
Tags: @product
1:24.309
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 51.545
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 23.418
And I take note of which tps features are available 0.636
Then a Tails persistence partition exists on USB drive "old" 0.526
And I shutdown Tails and wait for the computer to power off 7.878
After features/support/hooks.rb:331 0.540
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.195
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.470
Then Tails is running from USB drive "old" 0.190
And all tps features are active 1.106
When I write some files expected to persist 1.215
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.360
And all persistent directories from the old Tails version have safe access rights 1.808
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.996
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.657
After features/support/hooks.rb:331 0.157
After features/support/hooks.rb:100 0.006
Tags: @product
2:8.696
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 without a persistent partition and stopped at Tails Greeter's login screen 7.878
And I log in to a new session 11.379
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.685
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.042
Then the running Tails is installed on USB drive "to_upgrade" 15.193
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 1.999
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.433
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.967
Then all tps features from the old Tails version are active 1.045
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.330
And the expected persistent files created with the old Tails version are present in the filesystem 1.050
And all persistent directories from the old Tails version have safe access rights 1.762
After features/support/hooks.rb:331 0.787
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:30.117
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.135
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
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.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.017
And Tor is ready 20.893
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.359
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.192
Given I shutdown Tails and wait for the computer to power off 19.899
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.246
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.131
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.202
When the network is plugged 0.019
And Tor is ready 20.057
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.228
Given I shutdown Tails and wait for the computer to power off 18.516
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.466
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.222
And the file system changes introduced in version 6.3~testoverlayfs are present 0.323
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.014
And Tor is ready 20.530
Then the Upgrader considers the system as up-to-date 0.100
# 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.142
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 0.889
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
24.225
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.366
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.043
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 16.159
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.374
After features/support/hooks.rb:331 0.996
After features/support/hooks.rb:100 0.000