Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 30 02 Jul 2026, 13:46

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:28.464 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:9.692
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.882
When I start Tails from USB drive "old" with network unplugged 51.138
Then the boot device has safe access rights 2.800
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:339 3.455
After features/support/hooks.rb:108 0.009
Tags: @product
1:38.448
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login 57.584
Then Tails is running from USB drive "old" 0.289
And I create a persistent partition 26.727
And I take note of which tps features are available 5.031
Then a Tails persistence partition exists on USB drive "old" 0.608
And I shutdown Tails and wait for the computer to power off 8.094
After features/support/hooks.rb:339 0.405
After features/support/hooks.rb:108 0.007
Tags: @product
1:46.946
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.059
Then Tails is running from USB drive "old" 0.280
And all tps features are active 6.089
When I write some files expected to persist 1.550
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 1.951
And I take note of which tps features are available 4.914
And I shutdown Tails and wait for the computer to power off 8.387
# 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" 13.041
After features/support/hooks.rb:339 0.454
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.269
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.431
And I log in to a new session 13.448
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.002
And I plug USB drive "to_upgrade" 2.270
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.592
Then the running Tails is installed on USB drive "to_upgrade" 17.059
And I unplug USB drive "to_upgrade" 0.167
And I unplug USB drive "__internal" 0.296
After features/support/hooks.rb:339 4.096
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.025
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.636
Then all tps features from the old Tails version are active 0.986
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.552
And the expected persistent files created with the old Tails version are present in the filesystem 1.163
And all persistent directories from the old Tails version have safe access rights 2.359
After features/support/hooks.rb:339 0.754
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
4:2.001
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.600
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
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.205
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.012
And Tor is ready 13.319
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.851
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.117
Given I shutdown Tails and wait for the computer to power off 7.094
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.896
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.338
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.236
When the network is plugged 0.027
And Tor is ready 11.243
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.839
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.981
Given I shutdown Tails and wait for the computer to power off 8.004
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.385
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.051
And the file system changes introduced in version 6.3~testoverlayfs are present 0.417
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.013
And Tor is ready 10.294
Then the Upgrader considers the system as up-to-date 10.555
# 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.345
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.446
After features/support/hooks.rb:339 0.985
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
21.080
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 7.581
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.734
After features/support/hooks.rb:339 0.685
After features/support/hooks.rb:108 0.000