Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 42 14 Jul 2026, 08:14

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:13.919 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:11.542
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.184
When I start Tails from USB drive "old" with network unplugged 53.657
Then the boot device has safe access rights 2.787
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.266
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:339 1.350
After features/support/hooks.rb:108 0.008
Tags: @product
1:27.782
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 52.687
Then Tails is running from USB drive "old" 0.203
And I create a persistent partition 25.419
And I take note of which tps features are available 4.739
Then a Tails persistence partition exists on USB drive "old" 0.576
And I shutdown Tails and wait for the computer to power off 4.079
After features/support/hooks.rb:339 0.631
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.773
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.226
Then Tails is running from USB drive "old" 0.256
And all tps features are active 4.693
When I write some files expected to persist 1.311
# 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.294
And all persistent directories from the old Tails version have safe access rights 1.856
And I take note of which tps features are available 3.842
And I shutdown Tails and wait for the computer to power off 7.921
# 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.127
After features/support/hooks.rb:339 0.588
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.622
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.089
And I log in to a new session 12.807
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.763
And I plug USB drive "to_upgrade" 2.200
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.005
Then the running Tails is installed on USB drive "to_upgrade" 15.463
And I unplug USB drive "to_upgrade" 0.151
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 2.134
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.229
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.491
Then all tps features from the old Tails version are active 1.013
And Tails is running from USB drive "to_upgrade" 0.260
And the boot device has safe access rights 2.563
And the expected persistent files created with the old Tails version are present in the filesystem 1.089
And all persistent directories from the old Tails version have safe access rights 1.745
After features/support/hooks.rb:339 0.475
After features/support/hooks.rb:108 0.005
4:14.911
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 with a persistent partition enabled and logged in 8.194
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.019
And Tor is ready 20.129
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.459
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.201
Given I shutdown Tails and wait for the computer to power off 9.481
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.712
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.948
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# 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.215
When the network is plugged 0.018
And Tor is ready 20.209
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.386
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.429
Given I shutdown Tails and wait for the computer to power off 8.194
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.583
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.243
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.195
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.016
And Tor is ready 10.909
Then the Upgrader considers the system as up-to-date 10.524
# 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.264
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.359
After features/support/hooks.rb:339 1.006
After features/support/hooks.rb:108 0.054
21.058
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 with a persistent partition enabled and logged in 7.431
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 11.235
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.990
After features/support/hooks.rb:339 0.716
After features/support/hooks.rb:108 0.000