Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 6 07 Jun 2026, 08:20

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:56.794 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:16.533
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.201
When I start Tails from USB drive "old" with network unplugged 56.971
Then the boot device has safe access rights 3.467
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:335 1.461
After features/support/hooks.rb:104 0.007
Tags: @product
1:28.703
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 57.586
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 25.331
And I take note of which tps features are available 0.404
Then a Tails persistence partition exists on USB drive "old" 0.694
And I shutdown Tails and wait for the computer to power off 4.356
After features/support/hooks.rb:335 0.162
After features/support/hooks.rb:104 0.006
Tags: @product
1:29.537
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.344
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.340
When I write some files expected to persist 1.606
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 2.186
And I take note of which tps features are available 0.186
And I shutdown Tails and wait for the computer to power off 4.508
# 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" 13.247
After features/support/hooks.rb:335 0.372
After features/support/hooks.rb:104 0.008
Tags: @product
2:14.314
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.014
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.392
And I log in to a new session 14.352
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.957
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.155
Then the running Tails is installed on USB drive "to_upgrade" 15.928
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:335 2.547
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.713
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.225
Then all tps features from the old Tails version are active 1.233
And Tails is running from USB drive "to_upgrade" 0.427
And the boot device has safe access rights 2.671
And the expected persistent files created with the old Tails version are present in the filesystem 1.113
And all persistent directories from the old Tails version have safe access rights 1.977
After features/support/hooks.rb:335 0.532
After features/support/hooks.rb:104 0.007
3:52.637
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.889
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.022
And Tor is ready 13.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.595
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.857
Given I shutdown Tails and wait for the computer to power off 9.832
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.589
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.450
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.178
# 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.288
When the network is plugged 0.014
And Tor is ready 10.107
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.888
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.936
Given I shutdown Tails and wait for the computer to power off 4.245
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.821
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.514
And the file system changes introduced in version 6.3~testoverlayfs are present 0.424
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.205
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.024
And Tor is ready 11.523
Then the Upgrader considers the system as up-to-date 10.628
# 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.713
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.396
After features/support/hooks.rb:335 0.870
After features/support/hooks.rb:104 0.020
21.355
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.583
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.328
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.023
After features/support/hooks.rb:335 0.891
After features/support/hooks.rb:104 0.000