Project Number Date
test_Tails_ISO_devel 4471 28 Jun 2026, 11:20

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:7.775 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:6.319
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.926
When I start Tails from USB drive "old" with network unplugged 47.593
Then the boot device has safe access rights 2.891
And Tails is running from USB drive "old" 0.215
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:339 1.392
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.382
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 54.477
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 25.426
And I take note of which tps features are available 4.554
Then a Tails persistence partition exists on USB drive "old" 0.521
And I shutdown Tails and wait for the computer to power off 8.026
After features/support/hooks.rb:339 0.578
After features/support/hooks.rb:108 0.007
Tags: @product
1:37.502
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.552
Then Tails is running from USB drive "old" 0.264
And all tps features are active 4.715
When I write some files expected to persist 1.275
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.321
And all persistent directories from the old Tails version have safe access rights 1.969
And I take note of which tps features are available 4.487
And I shutdown Tails and wait for the computer to power off 4.342
# 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.345
After features/support/hooks.rb:339 0.340
After features/support/hooks.rb:108 0.007
Tags: @product
2:15.134
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.523
And I log in to a new session 14.833
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.968
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.509
Then the running Tails is installed on USB drive "to_upgrade" 16.780
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:339 2.105
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.963
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.703
Then all tps features from the old Tails version are active 1.058
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.723
And the expected persistent files created with the old Tails version are present in the filesystem 1.161
And all persistent directories from the old Tails version have safe access rights 2.026
After features/support/hooks.rb:339 0.839
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:59.875
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.037
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
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.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.019
And Tor is ready 12.705
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.345
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.892
Given I shutdown Tails and wait for the computer to power off 6.979
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.532
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.509
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
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.143
# 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.233
When the network is plugged 0.019
And Tor is ready 11.555
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.462
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.959
Given I shutdown Tails and wait for the computer to power off 8.167
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.464
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.737
And the file system changes introduced in version 6.3~testoverlayfs are present 0.348
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.017
And Tor is ready 10.198
Then the Upgrader considers the system as up-to-date 10.627
# 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.620
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.419
After features/support/hooks.rb:339 1.123
After features/support/hooks.rb:108 0.029
Tags: @product @automatic_upgrade
20.599
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.478
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.111
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 10.177
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.404
After features/support/hooks.rb:339 0.627
After features/support/hooks.rb:108 0.000