Project Number Date
test_Tails_ISO_21523-21524-unsafe-browser-onionshare-no-dbus-access 2 20 Apr 2026, 22:16

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:41.174 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:17.300
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.094
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" 15.217
When I start Tails from USB drive "old" with network unplugged 57.043
Then the boot device has safe access rights 3.145
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 3.834
After features/support/hooks.rb:100 0.007
Tags: @product
1:36.815
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 1:0.921
Then Tails is running from USB drive "old" 0.464
And I create a persistent partition 25.291
And I take note of which tps features are available 0.992
Then a Tails persistence partition exists on USB drive "old" 0.621
And I shutdown Tails and wait for the computer to power off 8.462
After features/support/hooks.rb:331 0.696
After features/support/hooks.rb:100 0.012
Tags: @product
1:33.781
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.388
Then Tails is running from USB drive "old" 0.254
And all tps features are active 1.094
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.223
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.000
And I take note of which tps features are available 0.201
And I shutdown Tails and wait for the computer to power off 4.336
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.538
After features/support/hooks.rb:331 0.605
After features/support/hooks.rb:100 0.006
Tags: @product
2:22.334
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.657
And I log in to a new session 16.478
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.567
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.087
Then the running Tails is installed on USB drive "to_upgrade" 18.778
And I unplug USB drive "to_upgrade" 0.174
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:331 4.437
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.515
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:12.472
Then all tps features from the old Tails version are active 1.078
And Tails is running from USB drive "to_upgrade" 0.282
And the boot device has safe access rights 3.008
And the expected persistent files created with the old Tails version are present in the filesystem 1.174
And all persistent directories from the old Tails version have safe access rights 2.430
After features/support/hooks.rb:331 0.842
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:59.186
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 9.166
And no SquashFS delta is installed 0.291
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.377
When the network is plugged 0.020
And Tor is ready 24.300
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.409
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.855
Given I shutdown Tails and wait for the computer to power off 16.600
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.038
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.177
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.185
# 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.292
When the network is plugged 0.015
And Tor is ready 21.316
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.389
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.571
Given I shutdown Tails and wait for the computer to power off 17.142
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.251
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.113
And the file system changes introduced in version 6.3~testoverlayfs are present 0.381
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.018
And Tor is ready 21.544
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.636
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.593
After features/support/hooks.rb:331 1.014
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
31.240
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 with a persistent partition enabled and logged in 8.618
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 21.859
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.393
After features/support/hooks.rb:331 1.053
After features/support/hooks.rb:100 0.000