Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 13 07 May 2026, 20:07

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:17.195 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:15.417
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.434
When I start Tails from USB drive "old" with network unplugged 57.633
Then the boot device has safe access rights 2.640
And Tails is running from USB drive "old" 0.197
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:331 3.696
After features/support/hooks.rb:100 0.006
Tags: @product
1:21.870
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 53.091
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 23.337
And I take note of which tps features are available 0.710
Then a Tails persistence partition exists on USB drive "old" 0.488
And I shutdown Tails and wait for the computer to power off 3.976
After features/support/hooks.rb:331 0.457
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.310
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.685
Then Tails is running from USB drive "old" 0.231
And all tps features are active 1.160
When I write some files expected to persist 1.254
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.556
And all persistent directories from the old Tails version have safe access rights 2.003
And I take note of which tps features are available 0.169
And I shutdown Tails and wait for the computer to power off 6.734
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.286
After features/support/hooks.rb:331 0.522
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.022
And I log in to a new session 12.716
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.728
And I plug USB drive "to_upgrade" 2.269
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.388
Then the running Tails is installed on USB drive "to_upgrade" 15.084
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 2.199
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.171
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.714
Then all tps features from the old Tails version are active 0.899
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.364
And the expected persistent files created with the old Tails version are present in the filesystem 1.115
And all persistent directories from the old Tails version have safe access rights 1.779
After features/support/hooks.rb:331 0.500
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:32.483
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.891
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.013
And Tor is ready 23.463
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.353
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.404
Given I shutdown Tails and wait for the computer to power off 19.972
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.450
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.125
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.193
When the network is plugged 0.017
And Tor is ready 21.647
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.370
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.159
Given I shutdown Tails and wait for the computer to power off 17.114
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.629
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.148
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.017
And Tor is ready 20.726
Then the Upgrader considers the system as up-to-date 0.099
# 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.285
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:331 0.935
After features/support/hooks.rb:100 0.045
Tags: @product @automatic_upgrade
26.446
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.138
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 18.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.344
After features/support/hooks.rb:331 0.777
After features/support/hooks.rb:100 0.000