Project Number Date
test_Tails_ISO_21565-flatpak-safe 86 12 Oct 2026, 12: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 12:15.582 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:17.435
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.095
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" 14.122
When I start Tails from USB drive "old" with network unplugged 58.621
Then the boot device has safe access rights 2.747
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.229
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 1.347
After features/support/hooks.rb:108 0.012
Tags: @product
1:30.815
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login 53.118
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 24.942
And I take note of which tps features are available 8.171
Then a Tails persistence partition exists on USB drive "old" 1.650
And I shutdown Tails and wait for the computer to power off 2.584
After features/support/hooks.rb:339 0.497
After features/support/hooks.rb:108 0.005
Tags: @product
1:48.841
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.815
Then Tails is running from USB drive "old" 0.282
And all tps features are active 10.116
When I write some files expected to persist 1.144
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.223
And all persistent directories from the old Tails version have safe access rights 1.597
And I take note of which tps features are available 10.370
And I shutdown Tails and wait for the computer to power off 4.016
# 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" 13.013
After features/support/hooks.rb:339 0.520
After features/support/hooks.rb:108 0.006
Tags: @product
2:20.003
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.830
And I log in to a new session 14.477
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.780
And I plug USB drive "to_upgrade" 2.281
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.371
Then the running Tails is installed on USB drive "to_upgrade" 20.975
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:339 3.638
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.869
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.133
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.739
Then all tps features from the old Tails version are active 1.085
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.740
And the expected persistent files created with the old Tails version are present in the filesystem 1.065
And all persistent directories from the old Tails version have safe access rights 1.881
After features/support/hooks.rb:339 0.872
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
3:46.502
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.597
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.170
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.316
When the network is plugged 0.031
And Tor is ready 13.202
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.167
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.020
Given I shutdown Tails and wait for the computer to power off 5.374
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.020
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.826
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.198
When the network is plugged 1.186
And Tor is ready 10.061
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.070
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.348
Given I shutdown Tails and wait for the computer to power off 2.644
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.232
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 10.080
And the file system changes introduced in version 6.3~testoverlayfs are present 0.335
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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.036
And Tor is ready 10.586
Then the Upgrader considers the system as up-to-date 0.148
# 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 4.281
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.467
After features/support/hooks.rb:339 1.018
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
19.114
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.996
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 10.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.321
After features/support/hooks.rb:339 0.558
After features/support/hooks.rb:108 0.000