Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 23 24 Jun 2026, 08:15

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 12:10.357 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.617
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.869
When I start Tails from USB drive "old" with network unplugged 49.960
Then the boot device has safe access rights 2.945
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.519
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.695
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 54.647
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 25.753
And I take note of which tps features are available 4.271
Then a Tails persistence partition exists on USB drive "old" 0.572
And I shutdown Tails and wait for the computer to power off 4.110
After features/support/hooks.rb:339 0.172
After features/support/hooks.rb:108 0.005
Tags: @product
1:43.049
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.973
Then Tails is running from USB drive "old" 0.285
And all tps features are active 5.394
When I write some files expected to persist 1.540
# 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.333
And all persistent directories from the old Tails version have safe access rights 1.852
And I take note of which tps features are available 4.091
And I shutdown Tails and wait for the computer to power off 8.028
# 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.286
After features/support/hooks.rb:339 0.309
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.775
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.369
And I log in to a new session 13.836
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.151
And I plug USB drive "to_upgrade" 2.365
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.764
Then the running Tails is installed on USB drive "to_upgrade" 16.027
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 1.959
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.146
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.164
Then all tps features from the old Tails version are active 1.354
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 3.086
And the expected persistent files created with the old Tails version are present in the filesystem 1.162
And all persistent directories from the old Tails version have safe access rights 2.037
After features/support/hooks.rb:339 0.638
After features/support/hooks.rb:108 0.006
4:1.280
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.403
And no SquashFS delta is installed 0.074
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.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.017
And Tor is ready 13.899
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.674
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.414
Given I shutdown Tails and wait for the computer to power off 10.004
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.747
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.218
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.222
When the network is plugged 0.039
And Tor is ready 9.873
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.611
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.479
Given I shutdown Tails and wait for the computer to power off 8.406
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.003
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.923
And the file system changes introduced in version 6.3~testoverlayfs are present 0.469
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.181
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.015
And Tor is ready 10.172
Then the Upgrader considers the system as up-to-date 10.578
# 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.647
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.432
After features/support/hooks.rb:339 0.642
After features/support/hooks.rb:108 0.011
19.791
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.204
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.200
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.955
After features/support/hooks.rb:339 0.958
After features/support/hooks.rb:108 0.000