Project Number Date
test_Tails_ISO_stable-flatpak 42 10 Oct 2026, 19:41

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:58.371 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:3.200
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.256
When I start Tails from USB drive "old" with network unplugged 45.906
Then the boot device has safe access rights 2.295
And Tails is running from USB drive "old" 0.196
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.148
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:339 3.861
After features/support/hooks.rb:108 0.010
Tags: @product
1:20.074
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 47.029
Then Tails is running from USB drive "old" 0.184
And I create a persistent partition 23.554
And I take note of which tps features are available 6.149
Then a Tails persistence partition exists on USB drive "old" 0.493
And I shutdown Tails and wait for the computer to power off 2.587
After features/support/hooks.rb:339 0.219
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.478
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.786
Then Tails is running from USB drive "old" 0.171
And all tps features are active 6.987
When I write some files expected to persist 1.175
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.124
And all persistence configuration files have safe access rights 0.221
And all persistent directories from the old Tails version have safe access rights 1.834
And I take note of which tps features are available 6.227
And I shutdown Tails and wait for the computer to power off 2.566
# 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.298
After features/support/hooks.rb:339 0.343
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.936
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.216
And I log in to a new session 11.526
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.614
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.870
Then the running Tails is installed on USB drive "to_upgrade" 18.260
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 1.677
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.250
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.243
Then all tps features from the old Tails version are active 0.952
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 1.896
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.768
After features/support/hooks.rb:339 0.844
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
3:27.608
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.140
And no SquashFS delta is installed 0.092
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.030
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.205
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.295
When the network is plugged 0.037
And Tor is ready 12.577
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.107
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.972
Given I shutdown Tails and wait for the computer to power off 5.214
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.041
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.698
And the file system changes introduced in version 6.2~testoverlayfs are present 0.149
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.097
# 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.170
When the network is plugged 0.048
And Tor is ready 11.235
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.407
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.571
Given I shutdown Tails and wait for the computer to power off 2.772
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.083
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.742
And the file system changes introduced in version 6.3~testoverlayfs are present 0.255
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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.141
When the network is plugged 0.033
And Tor is ready 11.168
Then the Upgrader considers the system as up-to-date 0.106
# 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.463
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.351
After features/support/hooks.rb:339 0.662
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
18.822
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.589
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 8.433
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.460
After features/support/hooks.rb:339 1.115
After features/support/hooks.rb:108 0.000