Project Number Date
test_Tails_ISO_21523-21524-unsafe-browser-onionshare-no-dbus-access 1 20 Apr 2026, 20:50

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:45.155 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:19.363
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.362
When I start Tails from USB drive "old" with network unplugged 59.417
Then the boot device has safe access rights 3.625
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.255
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:331 1.582
After features/support/hooks.rb:100 0.015
Tags: @product
1:35.282
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 59.098
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 26.068
And I take note of which tps features are available 0.825
Then a Tails persistence partition exists on USB drive "old" 0.566
And I shutdown Tails and wait for the computer to power off 8.306
After features/support/hooks.rb:331 0.755
After features/support/hooks.rb:100 0.009
Tags: @product
1:36.322
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.326
Then Tails is running from USB drive "old" 0.392
And all tps features are active 1.214
When I write some files expected to persist 1.361
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.491
And all persistent directories from the old Tails version have safe access rights 2.200
And I take note of which tps features are available 0.184
And I shutdown Tails and wait for the computer to power off 8.563
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.324
After features/support/hooks.rb:331 0.505
After features/support/hooks.rb:100 0.007
Tags: @product
2:21.903
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 8.154
And I log in to a new session 16.403
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.872
And I plug USB drive "to_upgrade" 2.322
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.274
Then the running Tails is installed on USB drive "to_upgrade" 18.544
And I unplug USB drive "to_upgrade" 0.168
And I unplug USB drive "__internal" 0.162
After features/support/hooks.rb:331 3.886
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.296
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.317
Then all tps features from the old Tails version are active 0.964
And Tails is running from USB drive "to_upgrade" 0.272
And the boot device has safe access rights 2.915
And the expected persistent files created with the old Tails version are present in the filesystem 1.281
And all persistent directories from the old Tails version have safe access rights 2.467
After features/support/hooks.rb:331 1.190
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:6.287
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.405
And no SquashFS delta is installed 0.191
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.585
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.059
And Tor is ready 23.797
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.438
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.681
Given I shutdown Tails and wait for the computer to power off 15.858
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.413
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.280
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.168
# 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.225
When the network is plugged 0.040
And Tor is ready 22.313
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.525
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.459
Given I shutdown Tails and wait for the computer to power off 12.788
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.404
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.449
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.161
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.017
And Tor is ready 20.633
Then the Upgrader considers the system as up-to-date 0.137
# 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.969
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.433
After features/support/hooks.rb:331 0.858
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
27.698
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 7.796
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 18.937
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.483
After features/support/hooks.rb:331 1.283
After features/support/hooks.rb:100 0.000