Project Number Date
test_Tails_ISO_devel 4182 22 Jan 2026, 12:00

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 16:13.955 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:32.200
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.996
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 28.364
When I start Tails from USB drive "old" with network unplugged 57.616
Then the boot device has safe access rights 3.171
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.095
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:331 4.235
After features/support/hooks.rb:100 0.030
Tags: @product
1:57.684
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 0.658
And I start Tails from USB drive "old" with network unplugged and I login 1:14.674
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 32.096
And I take note of which tps features are available 1.414
Then a Tails persistence partition exists on USB drive "old" 0.780
And I shutdown Tails and wait for the computer to power off 7.700
After features/support/hooks.rb:331 0.656
After features/support/hooks.rb:100 0.012
Tags: @product
2:4.870
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:28.700
Then Tails is running from USB drive "old" 0.684
And all tps features are active 2.006
When I write some files expected to persist 1.526
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.232
And I take note of which tps features are available 0.652
And I shutdown Tails and wait for the computer to power off 8.629
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.606
After features/support/hooks.rb:331 0.192
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.134
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.103
And I log in to a new session 14.226
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.615
And I plug USB drive "to_upgrade" 4.832
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.919
Then the running Tails is installed on USB drive "to_upgrade" 22.466
And I unplug USB drive "to_upgrade" 1.810
And I unplug USB drive "__internal" 1.159
After features/support/hooks.rb:331 6.371
After features/support/hooks.rb:100 0.000
Tags: @product
1:31.693
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:21.366
Then all tps features from the old Tails version are active 1.477
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.357
And the expected persistent files created with the old Tails version are present in the filesystem 1.489
And all persistent directories from the old Tails version have safe access rights 3.487
After features/support/hooks.rb:331 0.850
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:35.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.546
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.059
And Tor is ready 44.064
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.650
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.804
Given I shutdown Tails and wait for the computer to power off 7.867
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.213
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.484
And the file system changes introduced in version 6.2~testoverlayfs are present 0.262
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.233
# 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.420
When the network is plugged 0.057
And Tor is ready 42.393
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.671
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.802
Given I shutdown Tails and wait for the computer to power off 9.487
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.483
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.582
And the file system changes introduced in version 6.3~testoverlayfs are present 0.544
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.208
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.072
And Tor is ready 12.871
Then the Upgrader considers the system as up-to-date 10.646
# 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.765
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.716
After features/support/hooks.rb:331 1.672
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
50.876
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.050
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.052
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 39.826
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.605
After features/support/hooks.rb:331 1.818
After features/support/hooks.rb:100 0.000