Project Number Date
test_Tails_ISO_stable-flatpak 35 03 Oct 2026, 19:38

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.203 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:10.393
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.185
When I start Tails from USB drive "old" with network unplugged 53.752
Then the boot device has safe access rights 1.794
And Tails is running from USB drive "old" 0.167
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.162
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 3.667
After features/support/hooks.rb:108 0.006
Tags: @product
1:21.137
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 46.252
Then Tails is running from USB drive "old" 0.221
And I create a persistent partition 23.906
And I take note of which tps features are available 6.248
Then a Tails persistence partition exists on USB drive "old" 0.509
And I shutdown Tails and wait for the computer to power off 3.917
After features/support/hooks.rb:339 0.234
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.176
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.775
Then Tails is running from USB drive "old" 0.157
And all tps features are active 6.690
When I write some files expected to persist 1.189
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 1.774
And I take note of which tps features are available 6.111
And I shutdown Tails and wait for the computer to power off 2.596
# 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.277
After features/support/hooks.rb:339 0.093
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.959
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.062
And I log in to a new session 10.058
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.634
And I plug USB drive "to_upgrade" 2.172
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.010
Then the running Tails is installed on USB drive "to_upgrade" 17.786
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 1.559
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.459
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.585
Then all tps features from the old Tails version are active 1.069
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 1.822
And the expected persistent files created with the old Tails version are present in the filesystem 1.027
And all persistent directories from the old Tails version have safe access rights 1.665
After features/support/hooks.rb:339 0.818
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:37.378
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.163
And no SquashFS delta is installed 0.049
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.034
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.245
When the network is plugged 0.037
And Tor is ready 13.820
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.391
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.792
Given I shutdown Tails and wait for the computer to power off 5.121
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.724
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.843
And the file system changes introduced in version 6.2~testoverlayfs are present 0.147
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.183
# 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.194
When the network is plugged 0.031
And Tor is ready 10.633
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.958
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.277
Given I shutdown Tails and wait for the computer to power off 4.087
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.497
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.296
And the file system changes introduced in version 6.3~testoverlayfs are present 0.263
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.075
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.035
And Tor is ready 10.004
Then the Upgrader considers the system as up-to-date 10.391
# 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.141
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.277
After features/support/hooks.rb:339 0.962
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.698
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.858
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 8.859
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.630
After features/support/hooks.rb:339 1.040
After features/support/hooks.rb:108 0.000