Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 14 15 Jun 2026, 08:05

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:32.999 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:3.828
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.135
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.251
When I start Tails from USB drive "old" with network unplugged 46.259
Then the boot device has safe access rights 2.476
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:339 3.763
After features/support/hooks.rb:108 0.016
Tags: @product
1:28.490
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.134
And I start Tails from USB drive "old" with network unplugged and I login 52.473
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 24.263
And I take note of which tps features are available 3.945
Then a Tails persistence partition exists on USB drive "old" 0.554
And I shutdown Tails and wait for the computer to power off 6.894
After features/support/hooks.rb:339 0.371
After features/support/hooks.rb:108 0.015
Tags: @product
1:30.354
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.836
Then Tails is running from USB drive "old" 0.245
And all tps features are active 4.490
When I write some files expected to persist 1.339
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 1.977
And I take note of which tps features are available 3.664
And I shutdown Tails and wait for the computer to power off 4.353
# 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.802
After features/support/hooks.rb:339 0.474
After features/support/hooks.rb:108 0.017
Tags: @product
2:9.120
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.297
And I log in to a new session 11.768
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.761
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.166
Then the running Tails is installed on USB drive "to_upgrade" 14.653
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.020
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.077
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.147
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.887
Then all tps features from the old Tails version are active 1.192
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.479
And the expected persistent files created with the old Tails version are present in the filesystem 1.094
And all persistent directories from the old Tails version have safe access rights 2.042
After features/support/hooks.rb:339 0.749
After features/support/hooks.rb:108 0.021
3:49.031
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 with a persistent partition enabled and logged in 8.375
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.014
And Tor is ready 13.767
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.005
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.791
Given I shutdown Tails and wait for the computer to power off 7.209
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.284
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.651
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.174
When the network is plugged 0.015
And Tor is ready 10.979
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.029
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.555
Given I shutdown Tails and wait for the computer to power off 8.374
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.601
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.939
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.015
And Tor is ready 10.136
Then the Upgrader considers the system as up-to-date 10.604
# 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 3.910
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.376
After features/support/hooks.rb:339 0.889
After features/support/hooks.rb:108 0.032
20.095
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.663
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
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.055
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 8.513
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.576
After features/support/hooks.rb:339 0.652
After features/support/hooks.rb:108 0.000