Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 64 16 Jun 2026, 15:19

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:4.778 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:20.869
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 13.566
When I start Tails from USB drive "old" with network unplugged 1:1.931
Then the boot device has safe access rights 3.137
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:339 1.632
After features/support/hooks.rb:108 0.019
Tags: @product
1:36.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 58.888
Then Tails is running from USB drive "old" 0.280
And I create a persistent partition 25.230
And I take note of which tps features are available 4.131
Then a Tails persistence partition exists on USB drive "old" 0.609
And I shutdown Tails and wait for the computer to power off 7.445
After features/support/hooks.rb:339 0.608
After features/support/hooks.rb:108 0.040
Tags: @product
1:48.793
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.439
Then Tails is running from USB drive "old" 0.266
And all tps features are active 6.004
When I write some files expected to persist 1.523
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.455
And I take note of which tps features are available 4.918
And I shutdown Tails and wait for the computer to power off 6.988
# 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" 13.397
After features/support/hooks.rb:339 0.571
After features/support/hooks.rb:108 0.018
Tags: @product
2:15.866
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 without a persistent partition and stopped at Tails Greeter's login screen 7.726
And I log in to a new session 14.356
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.943
And I plug USB drive "to_upgrade" 2.298
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.486
Then the running Tails is installed on USB drive "to_upgrade" 16.697
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:339 3.157
After features/support/hooks.rb:108 0.000
Tags: @product
1:20.999
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.134
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.600
Then all tps features from the old Tails version are active 1.086
And Tails is running from USB drive "to_upgrade" 0.272
And the boot device has safe access rights 2.784
And the expected persistent files created with the old Tails version are present in the filesystem 1.142
And all persistent directories from the old Tails version have safe access rights 1.977
After features/support/hooks.rb:339 0.757
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
4:20.641
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.801
And no SquashFS delta is installed 0.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.014
And Tor is ready 14.177
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.818
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.645
Given I shutdown Tails and wait for the computer to power off 9.906
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.039
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.724
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.366
When the network is plugged 0.015
And Tor is ready 10.205
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.576
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.524
Given I shutdown Tails and wait for the computer to power off 4.937
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.137
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 6.140
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.023
And Tor is ready 10.245
Then the Upgrader considers the system as up-to-date 10.711
# 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.410
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.409
After features/support/hooks.rb:339 0.964
After features/support/hooks.rb:108 0.044
Tags: @product @automatic_upgrade
20.853
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.069
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.283
After features/support/hooks.rb:339 1.093
After features/support/hooks.rb:108 0.000