Project Number Date
test_Tails_ISO_21565-flatpak-safe 117 02 Nov 2026, 20:42

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:52.762 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.158
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.039
When I start Tails from USB drive "old" with network unplugged 52.307
Then the boot device has safe access rights 2.121
And Tails is running from USB drive "old" 0.217
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.035
And udev-watchdog is monitoring the correct device 0.158
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 1.783
After features/support/hooks.rb:108 0.006
Tags: @product
1:17.749
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login 46.401
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 22.186
And I take note of which tps features are available 5.825
Then a Tails persistence partition exists on USB drive "old" 0.451
And I shutdown Tails and wait for the computer to power off 2.562
After features/support/hooks.rb:339 0.579
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.110
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.558
Then Tails is running from USB drive "old" 0.201
And all tps features are active 7.006
When I write some files expected to persist 1.008
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.140
And all persistence configuration files have safe access rights 0.224
And all persistent directories from the old Tails version have safe access rights 1.602
And I take note of which tps features are available 5.515
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.265
After features/support/hooks.rb:339 0.156
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.434
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.255
And I log in to a new session 12.141
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.627
And I plug USB drive "to_upgrade" 2.603
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.459
Then the running Tails is installed on USB drive "to_upgrade" 18.097
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.893
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.303
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.514
Then all tps features from the old Tails version are active 1.178
And Tails is running from USB drive "to_upgrade" 0.194
And the boot device has safe access rights 1.994
And the expected persistent files created with the old Tails version are present in the filesystem 0.805
And all persistent directories from the old Tails version have safe access rights 1.505
After features/support/hooks.rb:339 0.938
After features/support/hooks.rb:108 0.005
3:21.897
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.937
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.295
When the network is plugged 0.035
And Tor is ready 11.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.974
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.047
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:1.767
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.406
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.098
# 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.149
When the network is plugged 0.026
And Tor is ready 10.103
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.296
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.721
Given I shutdown Tails and wait for the computer to power off 3.884
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.543
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.230
And the file system changes introduced in version 6.3~testoverlayfs are present 0.288
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.133
When the network is plugged 0.033
And Tor is ready 10.359
Then the Upgrader considers the system as up-to-date 0.114
# 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.121
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.319
After features/support/hooks.rb:339 0.861
After features/support/hooks.rb:108 0.008
19.107
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.743
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 10.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.830
After features/support/hooks.rb:339 0.604
After features/support/hooks.rb:108 0.000