Project Number Date
test_Tails_ISO_21565-flatpak-safe 78 07 Oct 2026, 18:33

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:20.258 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:13.404
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.576
When I start Tails from USB drive "old" with network unplugged 55.587
Then the boot device has safe access rights 2.518
And Tails is running from USB drive "old" 0.207
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.165
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 1.154
After features/support/hooks.rb:108 0.006
Tags: @product
1:23.532
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 48.836
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 23.570
And I take note of which tps features are available 6.294
Then a Tails persistence partition exists on USB drive "old" 0.432
And I shutdown Tails and wait for the computer to power off 4.084
After features/support/hooks.rb:339 0.305
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.495
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.270
Then Tails is running from USB drive "old" 0.186
And all tps features are active 8.135
When I write some files expected to persist 1.323
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.281
And all persistent directories from the old Tails version have safe access rights 1.882
And I take note of which tps features are available 6.071
And I shutdown Tails and wait for the computer to power off 4.209
# 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.886
After features/support/hooks.rb:339 0.310
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.899
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 without a persistent partition and stopped at Tails Greeter's login screen 8.237
And I log in to a new session 12.757
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.619
And I plug USB drive "to_upgrade" 2.205
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.456
Then the running Tails is installed on USB drive "to_upgrade" 18.366
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 2.129
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.191
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.273
Then all tps features from the old Tails version are active 1.156
And Tails is running from USB drive "to_upgrade" 0.178
And the boot device has safe access rights 2.102
And the expected persistent files created with the old Tails version are present in the filesystem 0.905
And all persistent directories from the old Tails version have safe access rights 1.487
After features/support/hooks.rb:339 0.475
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
3:29.949
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.227
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.033
And Tor is ready 12.887
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.345
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.663
Given I shutdown Tails and wait for the computer to power off 5.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.355
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.091
And the file system changes introduced in version 6.2~testoverlayfs are present 0.361
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.273
When the network is plugged 0.025
And Tor is ready 10.261
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.303
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.475
Given I shutdown Tails and wait for the computer to power off 2.548
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.301
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.273
And the file system changes introduced in version 6.3~testoverlayfs are present 0.333
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.024
And Tor is ready 10.407
Then the Upgrader considers the system as up-to-date 0.093
# 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.182
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:339 0.968
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
17.784
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 7.794
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 8.198
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.472
After features/support/hooks.rb:339 0.914
After features/support/hooks.rb:108 0.000