Project Number Date
test_Tails_ISO_21523-21524-unsafe-browser-onionshare-no-dbus-access 6 23 Apr 2026, 18:43

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:0.189 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:21.086
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
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" 13.399
When I start Tails from USB drive "old" with network unplugged 1:3.205
Then the boot device has safe access rights 2.741
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 1.179
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.785
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.744
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 23.643
And I take note of which tps features are available 0.723
Then a Tails persistence partition exists on USB drive "old" 0.485
And I shutdown Tails and wait for the computer to power off 7.908
After features/support/hooks.rb:331 0.611
After features/support/hooks.rb:100 0.008
Tags: @product
1:26.219
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.642
Then Tails is running from USB drive "old" 0.222
And all tps features are active 1.144
When I write some files expected to persist 1.267
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.494
And all persistent directories from the old Tails version have safe access rights 1.871
And I take note of which tps features are available 0.172
And I shutdown Tails and wait for the computer to power off 7.868
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.310
After features/support/hooks.rb:331 0.603
After features/support/hooks.rb:100 0.007
Tags: @product
2:19.063
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.640
And I log in to a new session 18.875
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.815
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.134
Then the running Tails is installed on USB drive "to_upgrade" 15.866
And I unplug USB drive "to_upgrade" 0.169
And I unplug USB drive "__internal" 0.296
After features/support/hooks.rb:331 7.599
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.022
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.165
Then all tps features from the old Tails version are active 1.126
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.460
And the expected persistent files created with the old Tails version are present in the filesystem 1.099
And all persistent directories from the old Tails version have safe access rights 1.854
After features/support/hooks.rb:331 0.663
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:45.209
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 21.141
And no SquashFS delta is installed 0.227
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.405
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.712
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.016
And Tor is ready 23.160
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.362
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.462
Given I shutdown Tails and wait for the computer to power off 22.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.273
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.149
And the file system changes introduced in version 6.2~testoverlayfs are present 0.197
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.183
When the network is plugged 0.015
And Tor is ready 21.426
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.361
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.001
Given I shutdown Tails and wait for the computer to power off 13.087
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.374
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.012
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.015
And Tor is ready 21.249
Then the Upgrader considers the system as up-to-date 0.100
# 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.236
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.351
After features/support/hooks.rb:331 0.802
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
27.801
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.866
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 19.037
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.471
After features/support/hooks.rb:331 1.485
After features/support/hooks.rb:100 0.000