Project Number Date
test_Tails_ISO_tor-browser-15.0.17 1 29 Jun 2026, 13:23

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:57.338 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:2.591
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.121
When I start Tails from USB drive "old" with network unplugged 44.020
Then the boot device has safe access rights 2.622
And Tails is running from USB drive "old" 0.254
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:339 1.211
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.624
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 54.093
Then Tails is running from USB drive "old" 0.212
And I create a persistent partition 25.036
And I take note of which tps features are available 4.616
Then a Tails persistence partition exists on USB drive "old" 0.565
And I shutdown Tails and wait for the computer to power off 8.043
After features/support/hooks.rb:339 0.341
After features/support/hooks.rb:108 0.010
Tags: @product
1:38.437
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.437
Then Tails is running from USB drive "old" 0.255
And all tps features are active 5.295
When I write some files expected to persist 1.405
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.276
And all persistent directories from the old Tails version have safe access rights 2.042
And I take note of which tps features are available 3.883
And I shutdown Tails and wait for the computer to power off 8.341
# 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.226
After features/support/hooks.rb:339 0.401
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.549
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.209
And I log in to a new session 12.184
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.740
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.286
Then the running Tails is installed on USB drive "to_upgrade" 15.596
And I unplug USB drive "to_upgrade" 0.157
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 2.052
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.807
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.409
Then all tps features from the old Tails version are active 0.927
And Tails is running from USB drive "to_upgrade" 0.262
And the boot device has safe access rights 2.648
And the expected persistent files created with the old Tails version are present in the filesystem 1.210
And all persistent directories from the old Tails version have safe access rights 2.293
After features/support/hooks.rb:339 0.883
After features/support/hooks.rb:108 0.072
3:57.040
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.302
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.013
And Tor is ready 12.049
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.509
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.810
Given I shutdown Tails and wait for the computer to power off 10.829
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.570
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.997
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.018
And Tor is ready 9.923
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.560
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.435
Given I shutdown Tails and wait for the computer to power off 7.979
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.965
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.357
And the file system changes introduced in version 6.3~testoverlayfs are present 0.399
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.028
And Tor is ready 9.963
Then the Upgrader considers the system as up-to-date 10.661
# 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.192
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:339 1.084
After features/support/hooks.rb:108 0.015
21.286
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.596
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 11.230
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.037
After features/support/hooks.rb:339 0.986
After features/support/hooks.rb:108 0.000