Project Number Date
test_Tails_ISO_tor-browser-15.0.17 4 30 Jun 2026, 02:58

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:35.393 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.174
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.175
When I start Tails from USB drive "old" with network unplugged 48.757
Then the boot device has safe access rights 2.552
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 1.218
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.675
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 51.738
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 23.485
And I take note of which tps features are available 3.693
Then a Tails persistence partition exists on USB drive "old" 0.486
And I shutdown Tails and wait for the computer to power off 7.967
After features/support/hooks.rb:339 0.224
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.658
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.647
Then Tails is running from USB drive "old" 0.209
And all tps features are active 4.907
When I write some files expected to persist 1.167
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.268
And all persistent directories from the old Tails version have safe access rights 1.934
And I take note of which tps features are available 3.886
And I shutdown Tails and wait for the computer to power off 6.755
# 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.634
After features/support/hooks.rb:339 0.167
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.105
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.322
And I log in to a new session 12.703
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.735
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.020
Then the running Tails is installed on USB drive "to_upgrade" 14.774
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:339 1.930
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.678
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:3.182
Then all tps features from the old Tails version are active 0.892
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.316
And the expected persistent files created with the old Tails version are present in the filesystem 1.099
And all persistent directories from the old Tails version have safe access rights 1.874
After features/support/hooks.rb:339 0.628
After features/support/hooks.rb:108 0.007
3:46.089
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.223
And no SquashFS delta is installed 0.119
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.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.014
And Tor is ready 12.895
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.949
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.230
Given I shutdown Tails and wait for the computer to power off 9.299
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.618
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.849
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.195
When the network is plugged 0.019
And Tor is ready 10.604
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.470
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.164
Given I shutdown Tails and wait for the computer to power off 7.881
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.759
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.433
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.059
And Tor is ready 11.063
Then the Upgrader considers the system as up-to-date 10.494
# 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.209
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 0.828
After features/support/hooks.rb:108 0.010
21.011
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.486
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.044
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.015
And Tor is ready 9.915
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.235
After features/support/hooks.rb:339 0.723
After features/support/hooks.rb:108 0.000