Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 19 20 Jun 2026, 08:19

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:10.631 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:6.030
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 13.900
When I start Tails from USB drive "old" with network unplugged 47.148
Then the boot device has safe access rights 2.862
And Tails is running from USB drive "old" 0.258
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.248
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.395
After features/support/hooks.rb:108 0.022
Tags: @product
1:31.678
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given a computer 0.156
And I start Tails from USB drive "old" with network unplugged and I login 54.102
Then Tails is running from USB drive "old" 0.423
And I create a persistent partition 25.581
And I take note of which tps features are available 4.052
Then a Tails persistence partition exists on USB drive "old" 0.497
And I shutdown Tails and wait for the computer to power off 6.864
After features/support/hooks.rb:339 0.188
After features/support/hooks.rb:108 0.018
Tags: @product
1:42.556
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.299
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.270
Then Tails is running from USB drive "old" 0.275
And all tps features are active 5.082
When I write some files expected to persist 1.411
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.337
And all persistent directories from the old Tails version have safe access rights 1.965
And I take note of which tps features are available 4.274
And I shutdown Tails and wait for the computer to power off 7.037
# 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" 12.433
After features/support/hooks.rb:339 0.382
After features/support/hooks.rb:108 0.018
Tags: @product
2:12.777
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.476
And I log in to a new session 13.289
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.921
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.559
Then the running Tails is installed on USB drive "to_upgrade" 15.979
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:339 4.112
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.722
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.896
Then all tps features from the old Tails version are active 1.006
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.559
And the expected persistent files created with the old Tails version are present in the filesystem 1.115
And all persistent directories from the old Tails version have safe access rights 1.736
After features/support/hooks.rb:339 0.490
After features/support/hooks.rb:108 0.018
4:2.801
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.482
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.390
When the network is plugged 0.015
And Tor is ready 12.273
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.853
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.988
Given I shutdown Tails and wait for the computer to power off 10.010
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.864
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 5.182
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.247
When the network is plugged 0.025
And Tor is ready 10.537
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.226
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.018
Given I shutdown Tails and wait for the computer to power off 8.503
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.363
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.431
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.016
And Tor is ready 10.181
Then the Upgrader considers the system as up-to-date 10.528
# 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.376
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:339 0.701
After features/support/hooks.rb:108 0.041
21.064
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.905
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.715
After features/support/hooks.rb:339 0.655
After features/support/hooks.rb:108 0.000