Project Number Date
test_Tails_ISO_21619-tor-browser-15.0.16 7 16 Jun 2026, 21:30

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:16.744 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:8.709
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.153
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.490
When I start Tails from USB drive "old" with network unplugged 50.734
Then the boot device has safe access rights 2.553
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.299
After features/support/hooks.rb:108 0.020
Tags: @product
1:32.727
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 55.205
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 27.258
And I take note of which tps features are available 4.731
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.547
After features/support/hooks.rb:339 0.184
After features/support/hooks.rb:108 0.035
Tags: @product
1:42.994
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.148
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.387
Then Tails is running from USB drive "old" 0.296
And all tps features are active 5.691
When I write some files expected to persist 1.368
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.370
And all persistent directories from the old Tails version have safe access rights 2.168
And I take note of which tps features are available 4.306
And I shutdown Tails and wait for the computer to power off 8.356
# 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.701
After features/support/hooks.rb:339 0.359
After features/support/hooks.rb:108 0.017
Tags: @product
2:13.376
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.427
And I log in to a new session 13.552
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.897
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.930
Then the running Tails is installed on USB drive "to_upgrade" 16.022
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.164
After features/support/hooks.rb:339 2.621
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.217
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.151
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.349
Then all tps features from the old Tails version are active 0.963
And Tails is running from USB drive "to_upgrade" 0.302
And the boot device has safe access rights 2.980
And the expected persistent files created with the old Tails version are present in the filesystem 1.192
And all persistent directories from the old Tails version have safe access rights 2.276
After features/support/hooks.rb:339 0.628
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
4:1.016
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.675
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.015
And Tor is ready 13.913
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.987
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.651
Given I shutdown Tails and wait for the computer to power off 10.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.587
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.267
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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 9.672
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.413
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.403
Given I shutdown Tails and wait for the computer to power off 8.532
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.308
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.494
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.013
And Tor is ready 9.662
Then the Upgrader considers the system as up-to-date 10.549
# 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.499
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.399
After features/support/hooks.rb:339 1.004
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
20.703
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.923
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
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.053
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.217
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.153
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.000