Project Number Date
test_Tails_ISO_torbrowser-launcher-merge-upstream-2026-08 1 06 Aug 2026, 17:32

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 11:13.449 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:18.624
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.029
When I start Tails from USB drive "old" with network unplugged 1:2.236
Then the boot device has safe access rights 1.690
And Tails is running from USB drive "old" 0.197
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.151
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 3.447
After features/support/hooks.rb:108 0.020
Tags: @product
1:18.545
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 47.761
Then Tails is running from USB drive "old" 0.211
And I create a persistent partition 21.679
And I take note of which tps features are available 5.778
Then a Tails persistence partition exists on USB drive "old" 0.479
And I shutdown Tails and wait for the computer to power off 2.560
After features/support/hooks.rb:339 0.295
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.854
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.118
Then Tails is running from USB drive "old" 0.192
And all tps features are active 7.171
When I write some files expected to persist 0.900
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.266
And all persistent directories from the old Tails version have safe access rights 1.409
And I take note of which tps features are available 5.914
And I shutdown Tails and wait for the computer to power off 2.512
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.135
After features/support/hooks.rb:339 0.482
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.068
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.171
And I log in to a new session 11.809
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.630
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.372
Then the running Tails is installed on USB drive "to_upgrade" 17.624
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 0.730
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.899
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.153
Then all tps features from the old Tails version are active 0.963
And Tails is running from USB drive "to_upgrade" 0.173
And the boot device has safe access rights 2.201
And the expected persistent files created with the old Tails version are present in the filesystem 0.894
And all persistent directories from the old Tails version have safe access rights 1.433
After features/support/hooks.rb:339 0.830
After features/support/hooks.rb:108 0.004
Tags: @product @automatic_upgrade
3:33.494
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.202
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.150
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.307
When the network is plugged 0.026
And Tor is ready 11.595
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.009
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.694
Given I shutdown Tails and wait for the computer to power off 5.204
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.624
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.660
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
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.092
# 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.189
When the network is plugged 0.041
And Tor is ready 10.006
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.434
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.536
Given I shutdown Tails and wait for the computer to power off 3.925
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.779
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.910
And the file system changes introduced in version 6.3~testoverlayfs are present 1.297
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.097
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.143
When the network is plugged 0.034
And Tor is ready 10.105
Then the Upgrader considers the system as up-to-date 10.415
# 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 3.050
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.319
After features/support/hooks.rb:339 0.871
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
17.963
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.033
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 8.742
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.865
After features/support/hooks.rb:339 0.701
After features/support/hooks.rb:108 0.000