Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 27 14 May 2026, 14:17

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 11:48.132 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:19.983
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.016
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.446
When I start Tails from USB drive "old" with network unplugged 1:1.933
Then the boot device has safe access rights 2.762
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:335 3.667
After features/support/hooks.rb:104 0.061
Tags: @product
1:29.169
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 53.928
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 25.683
And I take note of which tps features are available 0.377
Then a Tails persistence partition exists on USB drive "old" 0.572
And I shutdown Tails and wait for the computer to power off 8.277
After features/support/hooks.rb:335 0.181
After features/support/hooks.rb:104 0.007
Tags: @product
1:29.038
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.665
Then Tails is running from USB drive "old" 0.249
And all tps features are active 1.324
When I write some files expected to persist 1.369
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 2.125
And I take note of which tps features are available 0.160
And I shutdown Tails and wait for the computer to power off 7.943
# 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.257
After features/support/hooks.rb:104 0.007
Tags: @product
2:11.964
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 7.695
And I log in to a new session 12.614
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.788
And I plug USB drive "to_upgrade" 2.265
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.766
Then the running Tails is installed on USB drive "to_upgrade" 16.555
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:335 2.402
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.160
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.234
Then all tps features from the old Tails version are active 0.976
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 2.534
And the expected persistent files created with the old Tails version are present in the filesystem 1.124
And all persistent directories from the old Tails version have safe access rights 1.982
After features/support/hooks.rb:335 0.527
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
3:44.321
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.521
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.139
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.015
And Tor is ready 12.902
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.027
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.858
Given I shutdown Tails and wait for the computer to power off 6.888
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.688
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.196
And the file system changes introduced in version 6.2~testoverlayfs are present 0.230
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.274
When the network is plugged 0.019
And Tor is ready 10.182
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.659
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.601
Given I shutdown Tails and wait for the computer to power off 8.070
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.565
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.371
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.030
And Tor is ready 10.353
Then the Upgrader considers the system as up-to-date 10.533
# 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.752
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.468
After features/support/hooks.rb:335 1.140
After features/support/hooks.rb:104 0.014
Tags: @product @automatic_upgrade
21.495
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 7.889
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.376
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.891
After features/support/hooks.rb:335 0.760
After features/support/hooks.rb:104 0.000