Project Number Date
test_Tails_ISO_21742-tor-browser-15.0.21 4 01 Sep 2026, 20:27

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:45.404 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:8.645
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 14.205
When I start Tails from USB drive "old" with network unplugged 50.430
Then the boot device has safe access rights 2.200
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.439
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.171
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 51.194
Then Tails is running from USB drive "old" 0.173
And I create a persistent partition 22.812
And I take note of which tps features are available 7.094
Then a Tails persistence partition exists on USB drive "old" 0.687
And I shutdown Tails and wait for the computer to power off 4.120
After features/support/hooks.rb:339 0.153
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.545
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.058
Then Tails is running from USB drive "old" 0.231
And all tps features are active 7.464
When I write some files expected to persist 1.234
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.275
And all persistent directories from the old Tails version have safe access rights 1.771
And I take note of which tps features are available 7.051
And I shutdown Tails and wait for the computer to power off 4.021
# 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.170
After features/support/hooks.rb:339 0.259
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.373
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.841
And I log in to a new session 12.362
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.910
And I plug USB drive "to_upgrade" 2.212
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.677
Then the running Tails is installed on USB drive "to_upgrade" 19.099
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:339 3.698
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.793
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.110
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.927
Then all tps features from the old Tails version are active 1.425
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.495
And the expected persistent files created with the old Tails version are present in the filesystem 0.976
And all persistent directories from the old Tails version have safe access rights 1.644
After features/support/hooks.rb:339 0.835
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:46.145
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 8.601
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.121
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.030
And Tor is ready 13.175
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.338
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.974
Given I shutdown Tails and wait for the computer to power off 7.128
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.765
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.979
And the file system changes introduced in version 6.2~testoverlayfs are present 0.206
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.150
# 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.188
When the network is plugged 0.035
And Tor is ready 10.653
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.919
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.606
Given I shutdown Tails and wait for the computer to power off 2.695
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.883
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.654
And the file system changes introduced in version 6.3~testoverlayfs are present 0.392
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.027
And Tor is ready 11.129
Then the Upgrader considers the system as up-to-date 0.110
# 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.175
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.598
After features/support/hooks.rb:339 0.802
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
19.729
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 8.395
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 8.288
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.685
After features/support/hooks.rb:339 1.013
After features/support/hooks.rb:108 0.000