Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 61 13 Jun 2026, 14:25

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:44.359 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:17.475
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.122
When I start Tails from USB drive "old" with network unplugged 59.944
Then the boot device has safe access rights 2.639
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:339 1.593
After features/support/hooks.rb:108 0.015
Tags: @product
1:28.895
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login 52.573
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 23.171
And I take note of which tps features are available 3.915
Then a Tails persistence partition exists on USB drive "old" 0.495
And I shutdown Tails and wait for the computer to power off 8.395
After features/support/hooks.rb:339 0.504
After features/support/hooks.rb:108 0.016
Tags: @product
1:35.308
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.136
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.944
Then Tails is running from USB drive "old" 0.219
And all tps features are active 4.832
When I write some files expected to persist 1.287
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.277
And all persistent directories from the old Tails version have safe access rights 1.666
And I take note of which tps features are available 3.649
And I shutdown Tails and wait for the computer to power off 8.389
# 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.740
After features/support/hooks.rb:339 0.532
After features/support/hooks.rb:108 0.016
Tags: @product
2:10.803
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.914
And I log in to a new session 12.257
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.743
And I plug USB drive "to_upgrade" 2.261
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.154
Then the running Tails is installed on USB drive "to_upgrade" 15.189
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 2.267
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.160
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.106
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.353
Then all tps features from the old Tails version are active 0.982
And Tails is running from USB drive "to_upgrade" 0.200
And the boot device has safe access rights 2.375
And the expected persistent files created with the old Tails version are present in the filesystem 1.190
And all persistent directories from the old Tails version have safe access rights 1.951
After features/support/hooks.rb:339 0.553
After features/support/hooks.rb:108 0.040
Tags: @product @automatic_upgrade
3:41.362
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.945
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.326
When the network is plugged 0.016
And Tor is ready 13.161
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.670
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.627
Given I shutdown Tails and wait for the computer to power off 5.550
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.059
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.755
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.198
When the network is plugged 0.022
And Tor is ready 9.657
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.421
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.746
Given I shutdown Tails and wait for the computer to power off 4.122
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.494
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.967
And the file system changes introduced in version 6.3~testoverlayfs are present 0.356
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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.015
And Tor is ready 9.684
Then the Upgrader considers the system as up-to-date 10.520
# 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.385
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.326
After features/support/hooks.rb:339 1.028
After features/support/hooks.rb:108 0.061
Tags: @product @automatic_upgrade
19.352
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.718
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.052
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.452
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.860
After features/support/hooks.rb:339 0.874
After features/support/hooks.rb:108 0.000