Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 45 26 May 2026, 18:40

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:8.060 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:23.866
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.015
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.015
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.652
When I start Tails from USB drive "old" with network unplugged 1:4.922
Then the boot device has safe access rights 3.378
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:335 3.780
After features/support/hooks.rb:104 0.029
Tags: @product
1:30.956
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 57.056
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 25.654
And I take note of which tps features are available 0.421
Then a Tails persistence partition exists on USB drive "old" 0.540
And I shutdown Tails and wait for the computer to power off 6.930
After features/support/hooks.rb:335 0.401
After features/support/hooks.rb:104 0.009
Tags: @product
1:34.270
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.647
Then Tails is running from USB drive "old" 0.298
And all tps features are active 1.136
When I write some files expected to persist 1.355
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.324
And all persistent directories from the old Tails version have safe access rights 2.123
And I take note of which tps features are available 0.204
And I shutdown Tails and wait for the computer to power off 8.287
# 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" 12.624
After features/support/hooks.rb:335 0.564
After features/support/hooks.rb:104 0.007
Tags: @product
2:11.907
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.290
And I log in to a new session 11.991
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.742
And I plug USB drive "to_upgrade" 2.318
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.553
Then the running Tails is installed on USB drive "to_upgrade" 15.708
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:335 2.136
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.536
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.066
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.509
Then all tps features from the old Tails version are active 1.184
And Tails is running from USB drive "to_upgrade" 0.240
And the boot device has safe access rights 2.894
And the expected persistent files created with the old Tails version are present in the filesystem 1.299
And all persistent directories from the old Tails version have safe access rights 2.339
After features/support/hooks.rb:335 0.741
After features/support/hooks.rb:104 0.013
3:52.922
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 with a persistent partition enabled and logged in 8.591
And no SquashFS delta is installed 0.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.176
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.017
And Tor is ready 12.688
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.401
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.577
Given I shutdown Tails and wait for the computer to power off 10.309
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.289
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.194
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.181
# 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.224
When the network is plugged 0.015
And Tor is ready 11.597
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.779
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.267
Given I shutdown Tails and wait for the computer to power off 8.620
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.072
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.247
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.190
When the network is plugged 0.016
And Tor is ready 11.701
Then the Upgrader considers the system as up-to-date 10.578
# 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.289
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:335 1.075
After features/support/hooks.rb:104 0.014
20.599
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.909
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.143
After features/support/hooks.rb:335 0.674
After features/support/hooks.rb:104 0.000