Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 70 22 Jun 2026, 14:28

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:50.013 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.387
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 12.977
When I start Tails from USB drive "old" with network unplugged 1:1.995
Then the boot device has safe access rights 2.664
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.919
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.699
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 52.012
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 24.784
And I take note of which tps features are available 3.948
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 8.082
After features/support/hooks.rb:339 0.152
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.415
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.931
Then Tails is running from USB drive "old" 0.242
And all tps features are active 5.264
When I write some files expected to persist 1.178
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 1.832
And I take note of which tps features are available 3.836
And I shutdown Tails and wait for the computer to power off 7.800
# 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" 11.752
After features/support/hooks.rb:339 0.469
After features/support/hooks.rb:108 0.008
Tags: @product
2:10.021
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 without a persistent partition and stopped at Tails Greeter's login screen 7.932
And I log in to a new session 12.984
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.636
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.290
Then the running Tails is installed on USB drive "to_upgrade" 14.688
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:339 2.507
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.916
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.231
Then all tps features from the old Tails version are active 0.911
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 2.574
And the expected persistent files created with the old Tails version are present in the filesystem 0.995
And all persistent directories from the old Tails version have safe access rights 1.835
After features/support/hooks.rb:339 0.778
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:45.702
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.915
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.024
And Tor is ready 13.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.678
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.383
Given I shutdown Tails and wait for the computer to power off 5.486
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.732
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.981
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.192
When the network is plugged 0.013
And Tor is ready 10.744
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.731
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.826
Given I shutdown Tails and wait for the computer to power off 8.097
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.972
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.617
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.014
And Tor is ready 12.023
Then the Upgrader considers the system as up-to-date 10.484
# 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.161
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.457
After features/support/hooks.rb:339 0.764
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.869
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.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.782
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.563
After features/support/hooks.rb:339 0.873
After features/support/hooks.rb:108 0.000