Project Number Date
test_Tails_ISO_stable-flatpak 48 16 Oct 2026, 19:39

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:55.440 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
53.965
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.253
When I start Tails from USB drive "old" with network unplugged 37.077
Then the boot device has safe access rights 1.927
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.174
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.569
After features/support/hooks.rb:108 0.006
Tags: @product
1:21.932
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.079
Then Tails is running from USB drive "old" 0.185
And I create a persistent partition 23.806
And I take note of which tps features are available 6.328
Then a Tails persistence partition exists on USB drive "old" 0.483
And I shutdown Tails and wait for the computer to power off 3.971
After features/support/hooks.rb:339 0.377
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.908
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.907
Then Tails is running from USB drive "old" 0.221
And all tps features are active 6.788
When I write some files expected to persist 1.537
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.136
And all persistence configuration files have safe access rights 0.265
And all persistent directories from the old Tails version have safe access rights 2.001
And I take note of which tps features are available 6.325
And I shutdown Tails and wait for the computer to power off 2.520
# 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.126
After features/support/hooks.rb:339 0.427
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.606
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.187
And I log in to a new session 10.113
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.609
And I plug USB drive "to_upgrade" 2.187
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.638
Then the running Tails is installed on USB drive "to_upgrade" 17.631
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.460
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.497
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.383
Then all tps features from the old Tails version are active 1.163
And Tails is running from USB drive "to_upgrade" 0.173
And the boot device has safe access rights 1.854
And the expected persistent files created with the old Tails version are present in the filesystem 1.011
And all persistent directories from the old Tails version have safe access rights 1.841
After features/support/hooks.rb:339 0.649
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:34.097
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.084
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.191
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.302
When the network is plugged 0.024
And Tor is ready 14.070
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.947
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.748
Given I shutdown Tails and wait for the computer to power off 6.694
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.930
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.775
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.197
When the network is plugged 0.027
And Tor is ready 11.142
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.295
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.674
Given I shutdown Tails and wait for the computer to power off 3.978
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.989
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 7.563
And the file system changes introduced in version 6.3~testoverlayfs are present 0.333
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.169
When the network is plugged 0.029
And Tor is ready 11.298
Then the Upgrader considers the system as up-to-date 0.090
# 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.384
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.307
After features/support/hooks.rb:339 0.748
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
19.430
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.676
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 10.441
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.971
After features/support/hooks.rb:339 0.819
After features/support/hooks.rb:108 0.000