Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 44 15 Jul 2026, 08:22

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:23.671 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:1.227
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.089
When I start Tails from USB drive "old" with network unplugged 42.585
Then the boot device has safe access rights 2.706
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.237
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:339 1.302
After features/support/hooks.rb:108 0.008
Tags: @product
1:33.105
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.116
And I start Tails from USB drive "old" with network unplugged and I login 54.734
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 24.746
And I take note of which tps features are available 4.370
Then a Tails persistence partition exists on USB drive "old" 0.547
And I shutdown Tails and wait for the computer to power off 8.309
After features/support/hooks.rb:339 0.324
After features/support/hooks.rb:108 0.006
Tags: @product
1:43.391
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.678
Then Tails is running from USB drive "old" 0.295
And all tps features are active 5.548
When I write some files expected to persist 1.399
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.321
And all persistent directories from the old Tails version have safe access rights 2.110
And I take note of which tps features are available 4.214
And I shutdown Tails and wait for the computer to power off 8.085
# 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.519
After features/support/hooks.rb:339 0.454
After features/support/hooks.rb:108 0.009
Tags: @product
2:12.766
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.326
And I log in to a new session 13.270
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.877
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.707
Then the running Tails is installed on USB drive "to_upgrade" 16.080
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 2.362
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.259
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.111
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.983
Then all tps features from the old Tails version are active 1.050
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.704
And the expected persistent files created with the old Tails version are present in the filesystem 1.226
And all persistent directories from the old Tails version have safe access rights 1.888
After features/support/hooks.rb:339 0.561
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
4:14.418
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.414
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.016
And Tor is ready 13.598
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.932
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 9.598
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.403
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.610
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.215
# 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.279
When the network is plugged 0.017
And Tor is ready 11.545
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.830
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.707
Given I shutdown Tails and wait for the computer to power off 8.157
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.014
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.527
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
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.174
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.374
When the network is plugged 0.015
And Tor is ready 10.468
Then the Upgrader considers the system as up-to-date 10.626
# 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.984
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.413
After features/support/hooks.rb:339 1.093
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
20.502
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.603
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.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.014
And Tor is ready 10.640
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.901
After features/support/hooks.rb:339 0.713
After features/support/hooks.rb:108 0.000