Project Number Date
test_Tails_ISO_21565-flatpak-safe 64 03 Oct 2026, 03:19

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:39.801 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.669
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.970
When I start Tails from USB drive "old" with network unplugged 47.807
Then the boot device has safe access rights 2.216
And Tails is running from USB drive "old" 0.165
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.423
After features/support/hooks.rb:108 0.027
Tags: @product
1:18.573
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 45.949
Then Tails is running from USB drive "old" 0.177
And I create a persistent partition 22.993
And I take note of which tps features are available 6.242
Then a Tails persistence partition exists on USB drive "old" 0.485
And I shutdown Tails and wait for the computer to power off 2.650
After features/support/hooks.rb:339 0.285
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.554
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.089
Then Tails is running from USB drive "old" 0.195
And all tps features are active 6.867
When I write some files expected to persist 0.968
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.131
And all persistence configuration files have safe access rights 0.221
And all persistent directories from the old Tails version have safe access rights 1.566
And I take note of which tps features are available 5.830
And I shutdown Tails and wait for the computer to power off 2.510
# 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.086
After features/support/hooks.rb:339 0.272
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.786
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.038
And I log in to a new session 11.633
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.590
And I plug USB drive "to_upgrade" 2.187
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.266
Then the running Tails is installed on USB drive "to_upgrade" 16.828
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 1.428
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.639
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.104
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.484
Then all tps features from the old Tails version are active 1.108
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 2.188
And the expected persistent files created with the old Tails version are present in the filesystem 1.059
And all persistent directories from the old Tails version have safe access rights 1.479
After features/support/hooks.rb:339 0.536
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:17.077
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.134
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.260
When the network is plugged 0.031
And Tor is ready 12.469
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.290
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.826
Given I shutdown Tails and wait for the computer to power off 5.206
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.181
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.356
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.080
# 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.129
When the network is plugged 0.033
And Tor is ready 10.271
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.320
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.856
Given I shutdown Tails and wait for the computer to power off 2.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.467
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.444
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.110
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.157
When the network is plugged 0.039
And Tor is ready 10.090
Then the Upgrader considers the system as up-to-date 0.096
# 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.095
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.353
After features/support/hooks.rb:339 0.688
After features/support/hooks.rb:108 0.029
Tags: @product @automatic_upgrade
17.501
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 7.637
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.180
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 8.058
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.503
After features/support/hooks.rb:339 0.631
After features/support/hooks.rb:108 0.000