Project Number Date
test_Tails_ISO_flatpak-whisperback 4 13 May 2026, 20:54

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:5.175 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:9.602
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 12.795
When I start Tails from USB drive "old" with network unplugged 52.276
Then the boot device has safe access rights 2.774
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:335 1.399
After features/support/hooks.rb:104 0.006
Tags: @product
1:21.622
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 52.897
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 24.733
And I take note of which tps features are available 0.346
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 2.826
After features/support/hooks.rb:335 0.243
After features/support/hooks.rb:104 0.006
Tags: @product
1:23.859
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.013
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.768
Then Tails is running from USB drive "old" 0.214
And all tps features are active 1.087
When I write some files expected to persist 1.254
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 1.864
And I take note of which tps features are available 0.147
And I shutdown Tails and wait for the computer to power off 7.910
# 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.026
After features/support/hooks.rb:335 0.436
After features/support/hooks.rb:104 0.006
Tags: @product
2:8.892
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 without a persistent partition and stopped at Tails Greeter's login screen 7.488
And I log in to a new session 12.050
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.682
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.231
Then the running Tails is installed on USB drive "to_upgrade" 14.955
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:335 2.910
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.853
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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:0.996
Then all tps features from the old Tails version are active 1.061
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 2.483
And the expected persistent files created with the old Tails version are present in the filesystem 1.063
And all persistent directories from the old Tails version have safe access rights 1.920
After features/support/hooks.rb:335 0.813
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:33.523
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 7.875
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.190
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.384
When the network is plugged 0.015
And Tor is ready 13.292
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.328
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.429
Given I shutdown Tails and wait for the computer to power off 9.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.325
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.105
And the file system changes introduced in version 6.2~testoverlayfs are present 0.206
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# 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.186
When the network is plugged 0.015
And Tor is ready 11.110
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.120
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.175
Given I shutdown Tails and wait for the computer to power off 7.866
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.891
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.059
And the file system changes introduced in version 6.3~testoverlayfs are present 0.311
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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.013
And Tor is ready 10.115
Then the Upgrader considers the system as up-to-date 10.592
# 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.109
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:335 0.940
After features/support/hooks.rb:104 0.015
Tags: @product @automatic_upgrade
19.819
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.190
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.832
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.477
After features/support/hooks.rb:335 0.906
After features/support/hooks.rb:104 0.000