Project Number Date
test_Tails_ISO_21565-flatpak-safe 90 16 Oct 2026, 03:24

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:26.847 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:23.256
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.120
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.694
When I start Tails from USB drive "old" with network unplugged 1:5.670
Then the boot device has safe access rights 2.148
And Tails is running from USB drive "old" 0.190
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.806
After features/support/hooks.rb:108 0.079
Tags: @product
1:21.868
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 49.228
Then Tails is running from USB drive "old" 0.204
And I create a persistent partition 23.096
And I take note of which tps features are available 6.121
Then a Tails persistence partition exists on USB drive "old" 0.536
And I shutdown Tails and wait for the computer to power off 2.598
After features/support/hooks.rb:339 0.549
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.391
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.289
Then Tails is running from USB drive "old" 0.268
And all tps features are active 7.009
When I write some files expected to persist 1.233
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 1.634
And I take note of which tps features are available 5.948
And I shutdown Tails and wait for the computer to power off 4.225
# 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.211
After features/support/hooks.rb:339 0.426
After features/support/hooks.rb:108 0.007
Tags: @product
2:12.472
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.702
And I log in to a new session 11.482
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.601
And I plug USB drive "to_upgrade" 2.331
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.368
Then the running Tails is installed on USB drive "to_upgrade" 17.717
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 1.921
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.875
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.607
Then all tps features from the old Tails version are active 1.154
And Tails is running from USB drive "to_upgrade" 0.188
And the boot device has safe access rights 2.129
And the expected persistent files created with the old Tails version are present in the filesystem 1.004
And all persistent directories from the old Tails version have safe access rights 1.707
After features/support/hooks.rb:339 0.819
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:27.075
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 with a persistent partition enabled and logged in 8.241
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.176
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.301
When the network is plugged 0.033
And Tor is ready 12.954
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.296
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.691
Given I shutdown Tails and wait for the computer to power off 5.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.090
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 9.506
And the file system changes introduced in version 6.2~testoverlayfs are present 0.200
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.179
When the network is plugged 0.028
And Tor is ready 10.285
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.326
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.584
Given I shutdown Tails and wait for the computer to power off 2.590
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.824
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.101
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.155
When the network is plugged 0.051
And Tor is ready 10.029
Then the Upgrader considers the system as up-to-date 0.075
# 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.670
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.315
After features/support/hooks.rb:339 0.757
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.907
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.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
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.045
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.933
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.539
After features/support/hooks.rb:339 0.840
After features/support/hooks.rb:108 0.000