Project Number Date
test_Tails_ISO_stable-flatpak 25 22 Sep 2026, 19:39

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:51.474 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
57.599
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.919
When I start Tails from USB drive "old" with network unplugged 41.024
Then the boot device has safe access rights 1.944
And Tails is running from USB drive "old" 0.193
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.026
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 1.871
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.573
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 47.036
Then Tails is running from USB drive "old" 0.203
And I create a persistent partition 23.405
And I take note of which tps features are available 6.420
Then a Tails persistence partition exists on USB drive "old" 0.484
And I shutdown Tails and wait for the computer to power off 3.948
After features/support/hooks.rb:339 0.269
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.506
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.608
Then Tails is running from USB drive "old" 0.191
And all tps features are active 6.759
When I write some files expected to persist 1.200
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.249
And all persistent directories from the old Tails version have safe access rights 1.687
And I take note of which tps features are available 5.921
And I shutdown Tails and wait for the computer to power off 2.525
# 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.120
After features/support/hooks.rb:339 0.294
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.270
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.213
And I log in to a new session 12.523
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.578
And I plug USB drive "to_upgrade" 2.396
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.414
Then the running Tails is installed on USB drive "to_upgrade" 16.901
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.598
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.047
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.113
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.908
Then all tps features from the old Tails version are active 0.913
And Tails is running from USB drive "to_upgrade" 0.152
And the boot device has safe access rights 2.057
And the expected persistent files created with the old Tails version are present in the filesystem 1.125
And all persistent directories from the old Tails version have safe access rights 1.776
After features/support/hooks.rb:339 0.627
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:27.442
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 8.201
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.174
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.248
When the network is plugged 0.026
And Tor is ready 14.034
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.470
Given I shutdown Tails and wait for the computer to power off 5.153
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.935
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.636
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.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.112
# 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.171
When the network is plugged 0.023
And Tor is ready 10.143
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.474
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.855
Given I shutdown Tails and wait for the computer to power off 4.030
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.513
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.445
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.035
# 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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.156
When the network is plugged 0.036
And Tor is ready 11.228
Then the Upgrader considers the system as up-to-date 0.094
# 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.547
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.314
After features/support/hooks.rb:339 0.957
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.034
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.749
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
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.040
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 8.814
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.166
After features/support/hooks.rb:339 0.615
After features/support/hooks.rb:108 0.000