Project Number Date
test_Tails_ISO_stable-flatpak 16 13 Sep 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 11:8.295 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:2.157
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.132
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 12.717
When I start Tails from USB drive "old" with network unplugged 45.794
Then the boot device has safe access rights 1.833
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.730
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.502
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 46.471
Then Tails is running from USB drive "old" 0.162
And I create a persistent partition 23.938
And I take note of which tps features are available 6.314
Then a Tails persistence partition exists on USB drive "old" 0.459
And I shutdown Tails and wait for the computer to power off 5.078
After features/support/hooks.rb:339 0.333
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.473
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.111
Then Tails is running from USB drive "old" 0.192
And all tps features are active 6.725
When I write some files expected to persist 1.251
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.193
And all persistent directories from the old Tails version have safe access rights 2.134
And I take note of which tps features are available 5.961
And I shutdown Tails and wait for the computer to power off 2.580
# 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.087
After features/support/hooks.rb:339 0.333
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.103
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.334
And I log in to a new session 11.048
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.615
And I plug USB drive "to_upgrade" 2.179
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.127
Then the running Tails is installed on USB drive "to_upgrade" 17.541
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.789
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.417
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.286
Then all tps features from the old Tails version are active 1.113
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 1.917
And the expected persistent files created with the old Tails version are present in the filesystem 1.042
And all persistent directories from the old Tails version have safe access rights 1.751
After features/support/hooks.rb:339 0.822
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:38.526
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.129
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
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.194
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.303
When the network is plugged 0.026
And Tor is ready 13.504
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.663
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.765
Given I shutdown Tails and wait for the computer to power off 5.228
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.482
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.736
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.079
# 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.152
When the network is plugged 0.030
And Tor is ready 10.037
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.996
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.870
Given I shutdown Tails and wait for the computer to power off 4.114
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.335
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.403
And the file system changes introduced in version 6.3~testoverlayfs are present 0.265
And only the 6.3~testoverlayfs SquashFS delta is installed 0.032
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.024
And Tor is ready 10.335
Then the Upgrader considers the system as up-to-date 10.460
# 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.105
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.318
After features/support/hooks.rb:339 0.916
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.115
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.820
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.033
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.278
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.720
After features/support/hooks.rb:339 0.800
After features/support/hooks.rb:108 0.000