Project Number Date
test_Tails_ISO_stable-flatpak 10 09 Sep 2026, 19:33

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 12:1.813 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:12.083
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.928
When I start Tails from USB drive "old" with network unplugged 53.167
Then the boot device has safe access rights 2.209
And Tails is running from USB drive "old" 0.215
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.466
After features/support/hooks.rb:108 0.007
Tags: @product
1:27.679
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 50.493
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 25.130
And I take note of which tps features are available 7.143
Then a Tails persistence partition exists on USB drive "old" 0.496
And I shutdown Tails and wait for the computer to power off 4.074
After features/support/hooks.rb:339 0.146
After features/support/hooks.rb:108 0.007
Tags: @product
1:37.437
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.221
Then Tails is running from USB drive "old" 0.242
And all tps features are active 7.550
When I write some files expected to persist 1.437
# 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.247
And all persistent directories from the old Tails version have safe access rights 1.912
And I take note of which tps features are available 6.130
And I shutdown Tails and wait for the computer to power off 2.725
# 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.695
After features/support/hooks.rb:339 0.378
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.025
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.350
And I log in to a new session 11.730
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.802
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.427
Then the running Tails is installed on USB drive "to_upgrade" 19.245
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.117
After features/support/hooks.rb:339 1.644
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.117
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.346
Then all tps features from the old Tails version are active 1.213
And Tails is running from USB drive "to_upgrade" 0.273
And the boot device has safe access rights 2.486
And the expected persistent files created with the old Tails version are present in the filesystem 1.377
And all persistent directories from the old Tails version have safe access rights 2.328
After features/support/hooks.rb:339 0.670
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:58.369
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.357
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.027
And Tor is ready 13.224
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.217
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.765
Given I shutdown Tails and wait for the computer to power off 8.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.856
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.865
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.113
# 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.197
When the network is plugged 0.026
And Tor is ready 10.698
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.921
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.944
Given I shutdown Tails and wait for the computer to power off 4.228
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.020
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.018
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.023
And Tor is ready 11.054
Then the Upgrader considers the system as up-to-date 10.499
# 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.786
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.339
After features/support/hooks.rb:339 1.021
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
22.099
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.349
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
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.028
And Tor is ready 10.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.764
After features/support/hooks.rb:339 0.795
After features/support/hooks.rb:108 0.000