Project Number Date
test_Tails_ISO_21742-tor-browser-15.0.21 5 01 Sep 2026, 20:29

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:51.033 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.459
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.977
When I start Tails from USB drive "old" with network unplugged 44.342
Then the boot device has safe access rights 2.352
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:339 1.090
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.322
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 51.584
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 23.933
And I take note of which tps features are available 6.506
Then a Tails persistence partition exists on USB drive "old" 0.603
And I shutdown Tails and wait for the computer to power off 4.354
After features/support/hooks.rb:339 0.520
After features/support/hooks.rb:108 0.006
Tags: @product
1:42.014
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.987
Then Tails is running from USB drive "old" 0.281
And all tps features are active 8.059
When I write some files expected to persist 1.456
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.141
And all persistence configuration files have safe access rights 0.343
And all persistent directories from the old Tails version have safe access rights 2.440
And I take note of which tps features are available 7.240
And I shutdown Tails and wait for the computer to power off 3.880
# 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.090
After features/support/hooks.rb:339 0.335
After features/support/hooks.rb:108 0.006
Tags: @product
2:18.499
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.717
And I log in to a new session 13.543
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.877
And I plug USB drive "to_upgrade" 2.197
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.010
Then the running Tails is installed on USB drive "to_upgrade" 20.885
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:339 1.561
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.295
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.734
Then all tps features from the old Tails version are active 1.310
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.556
And the expected persistent files created with the old Tails version are present in the filesystem 1.142
And all persistent directories from the old Tails version have safe access rights 2.212
After features/support/hooks.rb:339 0.952
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:45.423
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 9.371
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
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.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.292
When the network is plugged 0.026
And Tor is ready 13.344
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.332
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.926
Given I shutdown Tails and wait for the computer to power off 5.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.705
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 8.377
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.100
# 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.178
When the network is plugged 0.031
And Tor is ready 10.704
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.065
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.802
Given I shutdown Tails and wait for the computer to power off 4.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.408
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.811
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.033
And Tor is ready 10.924
Then the Upgrader considers the system as up-to-date 0.127
# 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.417
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.504
After features/support/hooks.rb:339 1.038
After features/support/hooks.rb:108 0.058
Tags: @product @automatic_upgrade
20.018
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.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.276
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.252
After features/support/hooks.rb:339 0.687
After features/support/hooks.rb:108 0.000