Project Number Date
test_Tails_ISO_21565-flatpak-safe 38 17 Sep 2026, 12:02

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:12.150 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:14.012
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.191
When I start Tails from USB drive "old" with network unplugged 57.333
Then the boot device has safe access rights 1.842
And Tails is running from USB drive "old" 0.177
And there is no persistence partition on USB drive "old" 0.031
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.143
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.508
After features/support/hooks.rb:108 0.052
Tags: @product
1:21.661
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 46.754
Then Tails is running from USB drive "old" 0.198
And I create a persistent partition 23.705
And I take note of which tps features are available 6.163
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 4.254
After features/support/hooks.rb:339 0.170
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.404
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.265
Then Tails is running from USB drive "old" 0.186
And all tps features are active 6.504
When I write some files expected to persist 0.926
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.127
And all persistence configuration files have safe access rights 0.216
And all persistent directories from the old Tails version have safe access rights 1.375
And I take note of which tps features are available 6.005
And I shutdown Tails and wait for the computer to power off 2.551
# 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.159
After features/support/hooks.rb:339 0.398
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.847
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.320
And I log in to a new session 12.717
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.687
And I plug USB drive "to_upgrade" 2.187
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.505
Then the running Tails is installed on USB drive "to_upgrade" 17.194
And I unplug USB drive "to_upgrade" 0.108
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.979
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.207
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.634
Then all tps features from the old Tails version are active 0.957
And Tails is running from USB drive "to_upgrade" 0.160
And the boot device has safe access rights 1.963
And the expected persistent files created with the old Tails version are present in the filesystem 0.960
And all persistent directories from the old Tails version have safe access rights 1.453
After features/support/hooks.rb:339 0.870
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:26.112
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.097
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
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.308
When the network is plugged 0.028
And Tor is ready 13.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.303
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.731
Given I shutdown Tails and wait for the computer to power off 5.196
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.183
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.024
And the file system changes introduced in version 6.2~testoverlayfs are present 0.154
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# 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.151
When the network is plugged 0.032
And Tor is ready 10.225
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.866
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.637
Given I shutdown Tails and wait for the computer to power off 3.922
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.803
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.018
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.083
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.144
When the network is plugged 0.021
And Tor is ready 10.470
Then the Upgrader considers the system as up-to-date 0.080
# 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.170
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:339 0.743
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.903
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.671
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.024
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 10.065
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.862
After features/support/hooks.rb:339 0.839
After features/support/hooks.rb:108 0.000