Project Number Date
test_Tails_ISO_21565-flatpak-safe 15 27 Aug 2026, 20:10

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 10:48.020 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:4.586
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.305
When I start Tails from USB drive "old" with network unplugged 47.885
Then the boot device has safe access rights 1.782
And Tails is running from USB drive "old" 0.191
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.033
And udev-watchdog is monitoring the correct device 0.138
And I unplug USB drive "old" 0.101
After features/support/hooks.rb:339 1.832
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.423
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 47.182
Then Tails is running from USB drive "old" 0.197
And I create a persistent partition 22.076
And I take note of which tps features are available 5.850
Then a Tails persistence partition exists on USB drive "old" 0.481
And I shutdown Tails and wait for the computer to power off 2.562
After features/support/hooks.rb:339 0.392
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.598
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.480
Then Tails is running from USB drive "old" 0.230
And all tps features are active 7.331
When I write some files expected to persist 1.151
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.226
And all persistent directories from the old Tails version have safe access rights 1.473
And I take note of which tps features are available 5.909
And I shutdown Tails and wait for the computer to power off 2.499
# 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.063
After features/support/hooks.rb:339 0.209
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.320
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 8.336
And I log in to a new session 12.064
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.652
And I plug USB drive "to_upgrade" 2.179
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:29.935
Then the running Tails is installed on USB drive "to_upgrade" 17.896
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 3.726
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.588
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.592
Then all tps features from the old Tails version are active 1.079
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.052
And the expected persistent files created with the old Tails version are present in the filesystem 0.939
And all persistent directories from the old Tails version have safe access rights 1.631
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:20.957
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 8.255
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.279
When the network is plugged 0.044
And Tor is ready 13.010
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.329
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.107
Given I shutdown Tails and wait for the computer to power off 5.230
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.592
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.364
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# 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.157
When the network is plugged 0.029
And Tor is ready 10.010
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.876
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.653
Given I shutdown Tails and wait for the computer to power off 2.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.181
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.095
And the file system changes introduced in version 6.3~testoverlayfs are present 0.248
And only the 6.3~testoverlayfs SquashFS delta is installed 0.033
# 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.077
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160
When the network is plugged 0.031
And Tor is ready 10.160
Then the Upgrader considers the system as up-to-date 0.084
# 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 3.083
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.338
After features/support/hooks.rb:339 0.862
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.546
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.789
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.046
And the signing key used by the Upgrader is outdated 0.030
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.453
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.968
After features/support/hooks.rb:339 0.587
After features/support/hooks.rb:108 0.000