Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 8 08 Jun 2026, 17:10

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:57.901 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:10.848
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given a computer 0.240
And I create a 7200 MiB disk named "old" 0.016
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.840
When I start Tails from USB drive "old" with network unplugged 51.770
Then the boot device has safe access rights 3.183
And Tails is running from USB drive "old" 0.260
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:335 1.352
After features/support/hooks.rb:104 0.006
Tags: @product
1:29.609
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 56.226
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 25.051
And I take note of which tps features are available 0.354
Then a Tails persistence partition exists on USB drive "old" 0.550
And I shutdown Tails and wait for the computer to power off 7.095
After features/support/hooks.rb:335 0.269
After features/support/hooks.rb:104 0.008
Tags: @product
1:32.770
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.327
Then Tails is running from USB drive "old" 0.333
And all tps features are active 1.388
When I write some files expected to persist 1.243
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 1.967
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 8.093
# 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.712
After features/support/hooks.rb:335 0.592
After features/support/hooks.rb:104 0.007
Tags: @product
2:15.736
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 without a persistent partition and stopped at Tails Greeter's login screen 7.853
And I log in to a new session 13.557
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.828
And I plug USB drive "to_upgrade" 2.259
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.066
Then the running Tails is installed on USB drive "to_upgrade" 17.858
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:335 2.200
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.546
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.848
Then all tps features from the old Tails version are active 1.406
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.559
And the expected persistent files created with the old Tails version are present in the filesystem 1.219
And all persistent directories from the old Tails version have safe access rights 2.220
After features/support/hooks.rb:335 0.817
After features/support/hooks.rb:104 0.035
Tags: @product @automatic_upgrade
3:51.825
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.635
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
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.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 0.019
And Tor is ready 14.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.708
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.945
Given I shutdown Tails and wait for the computer to power off 9.885
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.069
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.396
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.177
# 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.235
When the network is plugged 0.020
And Tor is ready 10.063
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.476
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.496
Given I shutdown Tails and wait for the computer to power off 8.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.412
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.221
And the file system changes introduced in version 6.3~testoverlayfs are present 0.370
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.019
And Tor is ready 11.811
Then the Upgrader considers the system as up-to-date 10.583
# 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.349
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.508
After features/support/hooks.rb:335 0.739
After features/support/hooks.rb:104 0.014
Tags: @product @automatic_upgrade
22.564
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.456
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 10.631
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.079
After features/support/hooks.rb:335 0.710
After features/support/hooks.rb:104 0.001