Project Number Date
test_Tails_ISO_21565-flatpak-safe 72 06 Oct 2026, 03:20

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:10.562 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.946
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 12.918
When I start Tails from USB drive "old" with network unplugged 53.295
Then the boot device has safe access rights 1.985
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.030
And process "udev-watchdog" is running 0.026
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.582
After features/support/hooks.rb:108 0.005
Tags: @product
1:17.306
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 46.149
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 21.954
And I take note of which tps features are available 5.814
Then a Tails persistence partition exists on USB drive "old" 0.471
And I shutdown Tails and wait for the computer to power off 2.633
After features/support/hooks.rb:339 0.515
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.395
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.339
Then Tails is running from USB drive "old" 0.175
And all tps features are active 6.576
When I write some files expected to persist 1.120
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.273
And all persistent directories from the old Tails version have safe access rights 1.479
And I take note of which tps features are available 5.553
And I shutdown Tails and wait for the computer to power off 2.508
# 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.125
After features/support/hooks.rb:339 0.408
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.365
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.247
And I log in to a new session 10.744
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.560
And I plug USB drive "to_upgrade" 2.172
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.860
Then the running Tails is installed on USB drive "to_upgrade" 17.500
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:339 1.931
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.834
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.193
Then all tps features from the old Tails version are active 1.054
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 1.971
And the expected persistent files created with the old Tails version are present in the filesystem 0.849
And all persistent directories from the old Tails version have safe access rights 1.453
After features/support/hooks.rb:339 0.839
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
3:40.172
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.866
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.024
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.273
When the network is plugged 0.025
And Tor is ready 12.728
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.897
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 24.173
Given I shutdown Tails and wait for the computer to power off 6.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.291
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.119
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.082
# 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.190
When the network is plugged 0.035
And Tor is ready 10.125
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.961
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.997
Given I shutdown Tails and wait for the computer to power off 2.560
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.232
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.421
And the file system changes introduced in version 6.3~testoverlayfs are present 0.286
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.084
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.137
When the network is plugged 0.033
And Tor is ready 10.125
Then the Upgrader considers the system as up-to-date 0.079
# 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 2.984
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.312
After features/support/hooks.rb:339 0.612
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.542
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.657
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 9.753
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.819
After features/support/hooks.rb:339 0.571
After features/support/hooks.rb:108 0.000