Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 76 28 Jun 2026, 14:30

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.400 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:10.115
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.755
When I start Tails from USB drive "old" with network unplugged 51.615
Then the boot device has safe access rights 2.949
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.160
After features/support/hooks.rb:339 1.591
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.832
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 54.236
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 24.302
And I take note of which tps features are available 3.983
Then a Tails persistence partition exists on USB drive "old" 0.608
And I shutdown Tails and wait for the computer to power off 8.402
After features/support/hooks.rb:339 0.550
After features/support/hooks.rb:108 0.007
Tags: @product
1:40.050
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.951
Then Tails is running from USB drive "old" 0.250
And all tps features are active 4.762
When I write some files expected to persist 1.338
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.156
And all persistence configuration files have safe access rights 0.324
And all persistent directories from the old Tails version have safe access rights 1.946
And I take note of which tps features are available 4.368
And I shutdown Tails and wait for the computer to power off 8.364
# 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.528
After features/support/hooks.rb:339 0.324
After features/support/hooks.rb:108 0.008
Tags: @product
2:11.390
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 7.922
And I log in to a new session 12.798
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.768
And I plug USB drive "to_upgrade" 2.257
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.753
Then the running Tails is installed on USB drive "to_upgrade" 15.588
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:339 2.355
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.626
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.527
Then all tps features from the old Tails version are active 1.169
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 2.609
And the expected persistent files created with the old Tails version are present in the filesystem 1.119
And all persistent directories from the old Tails version have safe access rights 1.871
After features/support/hooks.rb:339 0.564
After features/support/hooks.rb:108 0.006
4:1.718
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 7.741
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.497
When the network is plugged 0.040
And Tor is ready 13.429
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.415
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.288
Given I shutdown Tails and wait for the computer to power off 9.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.444
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.243
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.179
When the network is plugged 0.016
And Tor is ready 9.583
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.365
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.651
Given I shutdown Tails and wait for the computer to power off 8.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.719
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.278
And the file system changes introduced in version 6.3~testoverlayfs are present 0.400
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.204
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.223
When the network is plugged 0.016
And Tor is ready 10.726
Then the Upgrader considers the system as up-to-date 10.549
# 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.105
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:339 0.727
After features/support/hooks.rb:108 0.010
20.666
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 7.496
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.480
After features/support/hooks.rb:339 0.538
After features/support/hooks.rb:108 0.000