Project Number Date
test_Tails_ISO_21565-flatpak-safe 130 07 Nov 2026, 03:34

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.178 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:8.450
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.178
When I start Tails from USB drive "old" with network unplugged 51.443
Then the boot device has safe access rights 2.080
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 1.575
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.685
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 47.770
Then Tails is running from USB drive "old" 0.167
And I create a persistent partition 23.112
And I take note of which tps features are available 6.109
Then a Tails persistence partition exists on USB drive "old" 0.462
And I shutdown Tails and wait for the computer to power off 3.983
After features/support/hooks.rb:339 0.153
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.163
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 with persistence enabled 58.868
Then Tails is running from USB drive "old" 0.212
And all tps features are active 6.733
When I write some files expected to persist 0.907
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.114
And all persistence configuration files have safe access rights 0.234
And all persistent directories from the old Tails version have safe access rights 1.370
And I take note of which tps features are available 6.226
And I shutdown Tails and wait for the computer to power off 5.025
# 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.394
After features/support/hooks.rb:339 0.170
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.168
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.331
And I log in to a new session 10.709
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.678
And I plug USB drive "to_upgrade" 2.310
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.905
Then the running Tails is installed on USB drive "to_upgrade" 18.013
And I unplug USB drive "to_upgrade" 0.110
And I unplug USB drive "__internal" 0.109
After features/support/hooks.rb:339 1.760
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.417
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.654
Then all tps features from the old Tails version are active 1.049
And Tails is running from USB drive "to_upgrade" 0.188
And the boot device has safe access rights 1.973
And the expected persistent files created with the old Tails version are present in the filesystem 0.828
And all persistent directories from the old Tails version have safe access rights 1.619
After features/support/hooks.rb:339 0.752
After features/support/hooks.rb:108 0.040
3:35.736
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 21.092
And no SquashFS delta is installed 0.043
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
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.307
When the network is plugged 0.025
And Tor is ready 12.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.864
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.879
Given I shutdown Tails and wait for the computer to power off 5.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.411
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.084
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.180
When the network is plugged 0.039
And Tor is ready 10.114
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.297
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.529
Given I shutdown Tails and wait for the computer to power off 3.893
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.745
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.442
And the file system changes introduced in version 6.3~testoverlayfs are present 0.288
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.031
And Tor is ready 9.938
Then the Upgrader considers the system as up-to-date 0.087
# 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.064
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.361
After features/support/hooks.rb:339 0.491
After features/support/hooks.rb:108 0.010
18.555
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.852
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 7.893
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.448
After features/support/hooks.rb:339 0.573
After features/support/hooks.rb:108 0.000