Project Number Date
test_Tails_ISO_21619-tor-browser-15.0.16 4 14 Jun 2026, 09:49

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:29.562 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.941
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.027
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 13.712
When I start Tails from USB drive "old" with network unplugged 57.513
Then the boot device has safe access rights 2.727
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:339 1.373
After features/support/hooks.rb:108 0.022
Tags: @product
1:33.877
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.260
And I start Tails from USB drive "old" with network unplugged and I login 55.349
Then Tails is running from USB drive "old" 0.240
And I create a persistent partition 24.744
And I take note of which tps features are available 3.888
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 8.860
After features/support/hooks.rb:339 0.517
After features/support/hooks.rb:108 0.027
Tags: @product
1:42.504
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.481
Then Tails is running from USB drive "old" 0.282
And all tps features are active 5.287
When I write some files expected to persist 1.354
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.345
And I take note of which tps features are available 4.487
And I shutdown Tails and wait for the computer to power off 6.930
# 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.437
After features/support/hooks.rb:339 0.464
After features/support/hooks.rb:108 0.030
Tags: @product
2:12.853
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.039
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.576
And I log in to a new session 13.099
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:32.305
Then the running Tails is installed on USB drive "to_upgrade" 15.462
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:339 2.338
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.006
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.023
Given a computer 0.157
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.141
Then all tps features from the old Tails version are active 1.002
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 2.316
And the expected persistent files created with the old Tails version are present in the filesystem 1.129
And all persistent directories from the old Tails version have safe access rights 2.047
After features/support/hooks.rb:339 0.764
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
4:7.130
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 9.233
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.015
And Tor is ready 13.976
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.486
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.893
Given I shutdown Tails and wait for the computer to power off 7.119
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.614
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.911
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.213
When the network is plugged 0.014
And Tor is ready 11.743
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.367
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.331
Given I shutdown Tails and wait for the computer to power off 7.641
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.973
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.249
And the file system changes introduced in version 6.3~testoverlayfs are present 0.345
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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.208
When the network is plugged 0.043
And Tor is ready 11.561
Then the Upgrader considers the system as up-to-date 10.778
# 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.207
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.489
After features/support/hooks.rb:339 1.041
After features/support/hooks.rb:108 0.048
Tags: @product @automatic_upgrade
21.249
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.658
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.887
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.273
After features/support/hooks.rb:339 0.991
After features/support/hooks.rb:108 0.000