Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 13 14 Jun 2026, 08:06

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:34.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:4.867
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.030
Given a computer 0.148
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.312
When I start Tails from USB drive "old" with network unplugged 46.894
Then the boot device has safe access rights 2.748
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:339 1.322
After features/support/hooks.rb:108 0.017
Tags: @product
1:28.862
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.035
Given a computer 0.139
And I start Tails from USB drive "old" with network unplugged and I login 52.174
Then Tails is running from USB drive "old" 0.226
And I create a persistent partition 24.852
And I take note of which tps features are available 4.141
Then a Tails persistence partition exists on USB drive "old" 0.581
And I shutdown Tails and wait for the computer to power off 6.746
After features/support/hooks.rb:339 0.471
After features/support/hooks.rb:108 0.018
Tags: @product
1:31.062
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.125
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.851
Then Tails is running from USB drive "old" 0.267
And all tps features are active 4.811
When I write some files expected to persist 1.485
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.338
And all persistent directories from the old Tails version have safe access rights 1.860
And I take note of which tps features are available 3.825
And I shutdown Tails and wait for the computer to power off 4.262
# 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.038
After features/support/hooks.rb:339 0.228
After features/support/hooks.rb:108 0.018
Tags: @product
2:9.104
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.858
And I log in to a new session 11.755
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.785
And I plug USB drive "to_upgrade" 2.196
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.262
Then the running Tails is installed on USB drive "to_upgrade" 14.973
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 2.062
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.310
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.115
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.594
Then all tps features from the old Tails version are active 0.973
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.502
And the expected persistent files created with the old Tails version are present in the filesystem 1.040
And all persistent directories from the old Tails version have safe access rights 1.879
After features/support/hooks.rb:339 0.923
After features/support/hooks.rb:108 0.018
3:51.196
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 8.312
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.343
When the network is plugged 0.016
And Tor is ready 12.267
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.628
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.245
Given I shutdown Tails and wait for the computer to power off 9.684
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.281
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.386
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.204
When the network is plugged 0.013
And Tor is ready 9.994
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.498
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.608
Given I shutdown Tails and wait for the computer to power off 8.565
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.108
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.674
And the file system changes introduced in version 6.3~testoverlayfs are present 0.392
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.017
And Tor is ready 10.865
Then the Upgrader considers the system as up-to-date 10.538
# 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 3.877
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.350
After features/support/hooks.rb:339 0.707
After features/support/hooks.rb:108 0.032
20.513
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 7.575
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.984
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.596
After features/support/hooks.rb:339 0.703
After features/support/hooks.rb:108 0.000