Project Number Date
test_Tails_ISO_stable 6452 17 Jun 2026, 07:48

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:46.331 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.620
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.033
Given a computer 0.239
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 14.015
When I start Tails from USB drive "old" with network unplugged 57.648
Then the boot device has safe access rights 2.759
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.243
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:339 3.567
After features/support/hooks.rb:108 0.023
Tags: @product
1:36.002
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 57.694
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 25.225
And I take note of which tps features are available 4.797
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 7.156
After features/support/hooks.rb:339 0.603
After features/support/hooks.rb:108 0.054
Tags: @product
1:42.429
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.050
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.096
Then Tails is running from USB drive "old" 0.252
And all tps features are active 4.982
When I write some files expected to persist 1.359
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.261
And all persistent directories from the old Tails version have safe access rights 2.113
And I take note of which tps features are available 4.668
And I shutdown Tails and wait for the computer to power off 4.575
# 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.733
After features/support/hooks.rb:339 0.499
After features/support/hooks.rb:108 0.043
Tags: @product
2:13.637
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.041
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.493
And I log in to a new session 13.074
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.845
And I plug USB drive "to_upgrade" 2.309
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.992
Then the running Tails is installed on USB drive "to_upgrade" 16.523
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:339 2.185
After features/support/hooks.rb:108 0.000
Tags: @product
1:19.553
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.026
Given a computer 0.351
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.842
Then all tps features from the old Tails version are active 1.084
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.683
And the expected persistent files created with the old Tails version are present in the filesystem 1.171
And all persistent directories from the old Tails version have safe access rights 2.182
After features/support/hooks.rb:339 0.698
After features/support/hooks.rb:108 0.045
Tags: @product @automatic_upgrade
4:15.744
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.031
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.187
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.324
When the network is plugged 0.019
And Tor is ready 12.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.905
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.214
Given I shutdown Tails and wait for the computer to power off 10.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.764
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 6.120
And the file system changes introduced in version 6.2~testoverlayfs are present 0.352
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.250
When the network is plugged 0.013
And Tor is ready 11.594
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.502
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.407
Given I shutdown Tails and wait for the computer to power off 7.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.621
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 6.044
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.046
# 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.167
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.018
And Tor is ready 10.147
Then the Upgrader considers the system as up-to-date 10.507
# 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.231
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.376
After features/support/hooks.rb:339 0.822
After features/support/hooks.rb:108 0.072
Tags: @product @automatic_upgrade
22.342
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.567
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
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.063
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.270
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.100
After features/support/hooks.rb:339 0.977
After features/support/hooks.rb:108 0.000