Project Number Date
test_Tails_ISO_devel 4680 19 Oct 2026, 11:22

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 10:36.812 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
58.503
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.927
When I start Tails from USB drive "old" with network unplugged 41.993
Then the boot device has safe access rights 1.820
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.145
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:339 3.532
After features/support/hooks.rb:108 0.014
Tags: @product
1:20.396
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 46.551
Then Tails is running from USB drive "old" 0.176
And I create a persistent partition 22.840
And I take note of which tps features are available 6.277
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 3.928
After features/support/hooks.rb:339 0.441
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.868
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.380
Then Tails is running from USB drive "old" 0.153
And all tps features are active 6.504
When I write some files expected to persist 0.946
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.142
And all persistence configuration files have safe access rights 0.175
And all persistent directories from the old Tails version have safe access rights 1.502
And I take note of which tps features are available 6.133
And I shutdown Tails and wait for the computer to power off 2.706
# 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" 11.133
After features/support/hooks.rb:339 0.398
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.328
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.078
And I log in to a new session 9.969
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.656
And I plug USB drive "to_upgrade" 2.185
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.371
Then the running Tails is installed on USB drive "to_upgrade" 17.834
And I unplug USB drive "to_upgrade" 0.107
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 1.699
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.040
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.626
Then all tps features from the old Tails version are active 1.025
And Tails is running from USB drive "to_upgrade" 0.157
And the boot device has safe access rights 1.846
And the expected persistent files created with the old Tails version are present in the filesystem 0.854
And all persistent directories from the old Tails version have safe access rights 1.446
After features/support/hooks.rb:339 0.595
After features/support/hooks.rb:108 0.058
Tags: @product @automatic_upgrade
3:16.390
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.990
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.175
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.249
When the network is plugged 0.023
And Tor is ready 13.152
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.289
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.890
Given I shutdown Tails and wait for the computer to power off 5.434
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.455
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.307
And the file system changes introduced in version 6.2~testoverlayfs are present 0.181
And only the 6.2~testoverlayfs SquashFS delta is installed 0.030
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.075
# 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.149
When the network is plugged 0.036
And Tor is ready 10.215
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.300
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.493
Given I shutdown Tails and wait for the computer to power off 2.514
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.358
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.385
And the file system changes introduced in version 6.3~testoverlayfs are present 0.284
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.085
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.031
And Tor is ready 10.213
Then the Upgrader considers the system as up-to-date 0.069
# 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.114
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.282
After features/support/hooks.rb:339 0.961
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.285
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.900
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.030
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 10.070
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.903
After features/support/hooks.rb:339 0.839
After features/support/hooks.rb:108 0.000