Project Number Date
test_Tails_ISO_21523-21524-unsafe-browser-onionshare-no-dbus-access 7 28 Apr 2026, 18:41

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:38.677 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:7.271
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.310
When I start Tails from USB drive "old" with network unplugged 49.441
Then the boot device has safe access rights 2.785
And Tails is running from USB drive "old" 0.236
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 3.823
After features/support/hooks.rb:100 0.023
Tags: @product
1:28.083
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 54.618
Then Tails is running from USB drive "old" 0.242
And I create a persistent partition 23.757
And I take note of which tps features are available 0.700
Then a Tails persistence partition exists on USB drive "old" 0.521
And I shutdown Tails and wait for the computer to power off 8.182
After features/support/hooks.rb:331 0.329
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.982
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.516
Then Tails is running from USB drive "old" 0.316
And all tps features are active 1.261
When I write some files expected to persist 1.335
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
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.882
And I take note of which tps features are available 0.173
And I shutdown Tails and wait for the computer to power off 4.140
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.662
After features/support/hooks.rb:331 0.318
After features/support/hooks.rb:100 0.007
Tags: @product
2:20.270
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.226
And I log in to a new session 19.669
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.824
And I plug USB drive "to_upgrade" 2.373
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.394
Then the running Tails is installed on USB drive "to_upgrade" 16.444
And I unplug USB drive "to_upgrade" 0.157
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:331 4.279
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.903
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.760
Then all tps features from the old Tails version are active 0.981
And Tails is running from USB drive "to_upgrade" 0.267
And the boot device has safe access rights 2.725
And the expected persistent files created with the old Tails version are present in the filesystem 1.164
And all persistent directories from the old Tails version have safe access rights 1.925
After features/support/hooks.rb:331 0.880
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
4:40.062
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 with a persistent partition enabled and logged in 8.447
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.019
And Tor is ready 28.560
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.414
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.926
Given I shutdown Tails and wait for the computer to power off 20.674
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.981
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.194
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
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.167
# 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.199
When the network is plugged 0.015
And Tor is ready 20.599
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.286
Given I shutdown Tails and wait for the computer to power off 11.898
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.938
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.067
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.013
And Tor is ready 21.242
Then the Upgrader considers the system as up-to-date 0.112
# 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.333
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.449
After features/support/hooks.rb:331 1.167
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
31.103
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 with a persistent partition enabled and logged in 7.764
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 22.526
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.379
After features/support/hooks.rb:331 0.638
After features/support/hooks.rb:100 0.000