Project Number Date
test_Tails_ISO_21523-21524-unsafe-browser-onionshare-no-dbus-access 11 02 May 2026, 18:45

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:35.529 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:23.842
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.991
When I start Tails from USB drive "old" with network unplugged 1:5.718
Then the boot device has safe access rights 2.396
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 3.784
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.345
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 57.305
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 23.593
And I take note of which tps features are available 0.665
Then a Tails persistence partition exists on USB drive "old" 0.533
And I shutdown Tails and wait for the computer to power off 7.991
After features/support/hooks.rb:331 0.590
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.370
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.965
Then Tails is running from USB drive "old" 0.219
And all tps features are active 1.125
When I write some files expected to persist 1.113
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 1.836
And I take note of which tps features are available 0.163
And I shutdown Tails and wait for the computer to power off 8.065
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.228
After features/support/hooks.rb:331 0.453
After features/support/hooks.rb:100 0.007
Tags: @product
2:15.007
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 7.528
And I log in to a new session 15.818
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.687
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.043
Then the running Tails is installed on USB drive "to_upgrade" 17.445
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 3.464
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.502
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.456
Then all tps features from the old Tails version are active 0.905
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 2.596
And the expected persistent files created with the old Tails version are present in the filesystem 1.203
And all persistent directories from the old Tails version have safe access rights 2.006
After features/support/hooks.rb:331 0.758
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:25.559
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.349
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.394
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.595
When the network is plugged 0.019
And Tor is ready 24.862
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.427
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.685
Given I shutdown Tails and wait for the computer to power off 19.206
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.702
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.144
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.193
When the network is plugged 0.015
And Tor is ready 20.304
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.431
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.015
Given I shutdown Tails and wait for the computer to power off 4.028
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.207
Then Tails is running version 6.3~testoverlayfs 0.050
And all tps features are active 1.105
And the file system changes introduced in version 6.3~testoverlayfs are present 0.407
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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.019
And Tor is ready 22.818
Then the Upgrader considers the system as up-to-date 0.124
# 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.714
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.464
After features/support/hooks.rb:331 0.965
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
26.902
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.221
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.048
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 18.966
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.363
After features/support/hooks.rb:331 0.801
After features/support/hooks.rb:100 0.000