Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 21 22 Jun 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:18.635 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:15.787
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.036
And I write an old version of the Tails USB image to disk "old" 13.938
When I start Tails from USB drive "old" with network unplugged 57.424
Then the boot device has safe access rights 2.475
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.227
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 1.610
After features/support/hooks.rb:108 0.018
Tags: @product
1:37.125
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login 56.877
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 25.993
And I take note of which tps features are available 4.796
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 8.445
After features/support/hooks.rb:339 0.287
After features/support/hooks.rb:108 0.019
Tags: @product
1:37.550
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.134
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.877
Then Tails is running from USB drive "old" 0.438
And all tps features are active 5.652
When I write some files expected to persist 1.386
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.356
And all persistent directories from the old Tails version have safe access rights 2.093
And I take note of which tps features are available 4.113
And I shutdown Tails and wait for the computer to power off 4.509
# 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.817
After features/support/hooks.rb:339 0.273
After features/support/hooks.rb:108 0.025
Tags: @product
2:12.375
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.419
And I log in to a new session 12.669
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.743
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.205
Then the running Tails is installed on USB drive "to_upgrade" 15.795
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:339 1.964
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.111
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.040
Given a computer 0.157
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.889
Then all tps features from the old Tails version are active 1.128
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.500
And the expected persistent files created with the old Tails version are present in the filesystem 1.112
And all persistent directories from the old Tails version have safe access rights 2.104
After features/support/hooks.rb:339 0.675
After features/support/hooks.rb:108 0.049
4:0.204
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.699
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.018
And Tor is ready 13.599
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.250
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.397
Given I shutdown Tails and wait for the computer to power off 6.985
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.470
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.186
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.281
When the network is plugged 0.016
And Tor is ready 11.839
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.918
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.821
Given I shutdown Tails and wait for the computer to power off 8.376
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.982
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 5.252
And the file system changes introduced in version 6.3~testoverlayfs are present 0.449
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.014
And Tor is ready 10.674
Then the Upgrader considers the system as up-to-date 10.620
# 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 5.054
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.458
After features/support/hooks.rb:339 0.772
After features/support/hooks.rb:108 0.040
20.480
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.850
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.191
After features/support/hooks.rb:339 0.816
After features/support/hooks.rb:108 0.000