Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 20 12 May 2026, 14: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 13:34.951 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:13.623
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.472
When I start Tails from USB drive "old" with network unplugged 54.068
Then the boot device has safe access rights 3.142
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.251
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:335 3.553
After features/support/hooks.rb:104 0.011
Tags: @product
1:41.258
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login 1:2.401
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 28.284
And I take note of which tps features are available 0.972
Then a Tails persistence partition exists on USB drive "old" 0.708
And I shutdown Tails and wait for the computer to power off 8.492
After features/support/hooks.rb:335 0.236
After features/support/hooks.rb:104 0.007
Tags: @product
1:37.705
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.466
Then Tails is running from USB drive "old" 0.572
And all tps features are active 1.545
When I write some files expected to persist 1.710
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.567
And all persistent directories from the old Tails version have safe access rights 2.177
And I take note of which tps features are available 0.219
And I shutdown Tails and wait for the computer to power off 8.277
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.899
After features/support/hooks.rb:335 0.160
After features/support/hooks.rb:104 0.008
Tags: @product
2:16.942
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.150
And I log in to a new session 14.912
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.758
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.346
Then the running Tails is installed on USB drive "to_upgrade" 17.172
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:335 2.645
After features/support/hooks.rb:104 0.000
Tags: @product
1:19.023
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.011
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.119
Then all tps features from the old Tails version are active 1.468
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.228
And the expected persistent files created with the old Tails version are present in the filesystem 1.412
And all persistent directories from the old Tails version have safe access rights 2.333
After features/support/hooks.rb:335 0.827
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
4:58.566
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.641
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.021
And Tor is ready 22.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.393
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.078
Given I shutdown Tails and wait for the computer to power off 20.104
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.136
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.394
And the file system changes introduced in version 6.2~testoverlayfs are present 0.254
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.208
When the network is plugged 0.017
And Tor is ready 21.525
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.421
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.934
Given I shutdown Tails and wait for the computer to power off 18.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.450
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.233
And the file system changes introduced in version 6.3~testoverlayfs are present 0.405
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.013
And Tor is ready 21.988
Then the Upgrader considers the system as up-to-date 0.138
# 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.411
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.508
After features/support/hooks.rb:335 1.075
After features/support/hooks.rb:104 0.018
Tags: @product @automatic_upgrade
27.831
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.953
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 19.033
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.432
After features/support/hooks.rb:335 1.069
After features/support/hooks.rb:104 0.000