Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 63 15 Jun 2026, 14:46

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:37.222 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:21.619
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.117
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.817
When I start Tails from USB drive "old" with network unplugged 1:3.172
Then the boot device has safe access rights 2.701
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.260
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 1.756
After features/support/hooks.rb:108 0.049
Tags: @product
1:35.700
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.145
And I start Tails from USB drive "old" with network unplugged and I login 56.840
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 25.953
And I take note of which tps features are available 4.777
Then a Tails persistence partition exists on USB drive "old" 0.656
And I shutdown Tails and wait for the computer to power off 7.068
After features/support/hooks.rb:339 0.172
After features/support/hooks.rb:108 0.017
Tags: @product
1:39.319
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.128
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.189
Then Tails is running from USB drive "old" 0.270
And all tps features are active 5.505
When I write some files expected to persist 1.240
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.134
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 1.980
And I take note of which tps features are available 4.218
And I shutdown Tails and wait for the computer to power off 4.544
# 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.748
After features/support/hooks.rb:339 0.529
After features/support/hooks.rb:108 0.017
Tags: @product
2:14.875
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.324
And I log in to a new session 14.530
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.103
And I plug USB drive "to_upgrade" 2.278
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.866
Then the running Tails is installed on USB drive "to_upgrade" 16.471
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:339 2.133
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.534
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.116
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.103
Then all tps features from the old Tails version are active 1.075
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 2.857
And the expected persistent files created with the old Tails version are present in the filesystem 1.216
And all persistent directories from the old Tails version have safe access rights 1.849
After features/support/hooks.rb:339 0.723
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
4:4.524
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.748
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.338
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.101
And Tor is ready 14.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.275
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.356
Given I shutdown Tails and wait for the computer to power off 9.910
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.365
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 5.762
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.274
When the network is plugged 0.019
And Tor is ready 10.520
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.232
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.233
Given I shutdown Tails and wait for the computer to power off 7.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.964
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.660
And the file system changes introduced in version 6.3~testoverlayfs are present 0.335
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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.015
And Tor is ready 10.164
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.415
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.456
After features/support/hooks.rb:339 0.901
After features/support/hooks.rb:108 0.031
Tags: @product @automatic_upgrade
22.648
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.530
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.336
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.337
After features/support/hooks.rb:339 0.598
After features/support/hooks.rb:108 0.000