Project Number Date
test_Tails_ISO_stable-flatpak 21 18 Sep 2026, 19:40

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:57.980 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
59.160
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.389
When I start Tails from USB drive "old" with network unplugged 42.478
Then the boot device has safe access rights 1.602
And Tails is running from USB drive "old" 0.178
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 1.611
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.807
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 46.167
Then Tails is running from USB drive "old" 0.214
And I create a persistent partition 23.845
And I take note of which tps features are available 6.041
Then a Tails persistence partition exists on USB drive "old" 0.425
And I shutdown Tails and wait for the computer to power off 5.037
After features/support/hooks.rb:339 0.492
After features/support/hooks.rb:108 0.021
Tags: @product
1:30.890
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.109
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.796
Then Tails is running from USB drive "old" 0.198
And all tps features are active 7.030
When I write some files expected to persist 1.255
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.108
And all persistence configuration files have safe access rights 0.246
And all persistent directories from the old Tails version have safe access rights 1.690
And I take note of which tps features are available 5.819
And I shutdown Tails and wait for the computer to power off 2.505
# 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.128
After features/support/hooks.rb:339 0.394
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.086
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.073
And I log in to a new session 11.178
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.604
And I plug USB drive "to_upgrade" 2.727
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.754
Then the running Tails is installed on USB drive "to_upgrade" 17.513
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.408
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.911
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.497
Then all tps features from the old Tails version are active 1.191
And Tails is running from USB drive "to_upgrade" 0.182
And the boot device has safe access rights 2.162
And the expected persistent files created with the old Tails version are present in the filesystem 1.106
And all persistent directories from the old Tails version have safe access rights 1.685
After features/support/hooks.rb:339 0.691
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:28.794
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.967
And no SquashFS delta is installed 0.051
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.031
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.312
When the network is plugged 0.024
And Tor is ready 13.777
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.461
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.290
Given I shutdown Tails and wait for the computer to power off 5.259
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.800
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.894
And the file system changes introduced in version 6.2~testoverlayfs are present 0.153
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.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.169
When the network is plugged 0.031
And Tor is ready 10.005
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.186
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.072
Given I shutdown Tails and wait for the computer to power off 3.951
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.900
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.565
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.040
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.022
And Tor is ready 10.754
Then the Upgrader considers the system as up-to-date 0.097
# 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.441
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.293
After features/support/hooks.rb:339 1.034
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.330
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.869
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.177
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 8.514
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.651
After features/support/hooks.rb:339 0.910
After features/support/hooks.rb:108 0.000