Project Number Date
test_Tails_ISO_stable 6415 01 Jun 2026, 15:11

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:30.628 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:3.850
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.811
When I start Tails from USB drive "old" with network unplugged 45.048
Then the boot device has safe access rights 3.148
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:335 1.526
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.113
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 54.350
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 25.398
And I take note of which tps features are available 0.326
Then a Tails persistence partition exists on USB drive "old" 0.556
And I shutdown Tails and wait for the computer to power off 4.153
After features/support/hooks.rb:335 0.286
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.003
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.662
Then Tails is running from USB drive "old" 0.218
And all tps features are active 1.189
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.284
And all persistent directories from the old Tails version have safe access rights 1.809
And I take note of which tps features are available 0.190
And I shutdown Tails and wait for the computer to power off 8.086
# 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.101
After features/support/hooks.rb:335 0.385
After features/support/hooks.rb:104 0.024
Tags: @product
2:10.783
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.899
And I log in to a new session 12.364
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.899
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.381
Then the running Tails is installed on USB drive "to_upgrade" 15.647
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:335 2.392
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.617
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.508
Then all tps features from the old Tails version are active 1.010
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 2.488
And the expected persistent files created with the old Tails version are present in the filesystem 1.166
And all persistent directories from the old Tails version have safe access rights 2.101
After features/support/hooks.rb:335 0.859
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:52.969
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.376
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.016
And Tor is ready 21.409
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.059
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.795
Given I shutdown Tails and wait for the computer to power off 9.517
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.598
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.250
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
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.161
# 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.196
When the network is plugged 0.015
And Tor is ready 10.553
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.239
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.930
Given I shutdown Tails and wait for the computer to power off 8.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.259
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.434
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.200
When the network is plugged 0.016
And Tor is ready 9.987
Then the Upgrader considers the system as up-to-date 10.564
# 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.797
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.389
After features/support/hooks.rb:335 0.938
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.291
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.499
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.131
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 8.473
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.851
After features/support/hooks.rb:335 0.938
After features/support/hooks.rb:104 0.000