Project Number Date
test_Tails_ISO_21523-21524-unsafe-browser-onionshare-no-dbus-access 10 01 May 2026, 18:19

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:3.151 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:3.691
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 12.822
When I start Tails from USB drive "old" with network unplugged 46.708
Then the boot device has safe access rights 2.444
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 1.386
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.599
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 51.266
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 23.048
And I take note of which tps features are available 0.618
Then a Tails persistence partition exists on USB drive "old" 0.495
And I shutdown Tails and wait for the computer to power off 7.887
After features/support/hooks.rb:331 0.258
After features/support/hooks.rb:100 0.008
Tags: @product
1:24.121
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.637
Then Tails is running from USB drive "old" 0.228
And all tps features are active 1.093
When I write some files expected to persist 1.492
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 1.829
And I take note of which tps features are available 0.170
And I shutdown Tails and wait for the computer to power off 8.133
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.875
After features/support/hooks.rb:331 0.241
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.780
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 without a persistent partition and stopped at Tails Greeter's login screen 8.002
And I log in to a new session 11.962
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.815
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.248
Then the running Tails is installed on USB drive "to_upgrade" 15.258
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 1.876
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.127
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.479
Then all tps features from the old Tails version are active 0.850
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.481
And the expected persistent files created with the old Tails version are present in the filesystem 1.076
And all persistent directories from the old Tails version have safe access rights 1.936
After features/support/hooks.rb:331 0.692
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:30.643
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.898
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.357
When the network is plugged 0.019
And Tor is ready 22.137
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.262
Given I shutdown Tails and wait for the computer to power off 19.800
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.463
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.037
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.196
When the network is plugged 0.023
And Tor is ready 21.361
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.874
Given I shutdown Tails and wait for the computer to power off 16.908
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.937
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.147
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.018
And Tor is ready 21.194
Then the Upgrader considers the system as up-to-date 0.099
# 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.154
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.318
After features/support/hooks.rb:331 0.843
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
25.187
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.408
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
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.043
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 17.028
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.363
After features/support/hooks.rb:331 1.012
After features/support/hooks.rb:100 0.000