Project Number Date
test_Tails_ISO_stable-flatpak 15 12 Sep 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 11:12.272 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:0.768
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.128
When I start Tails from USB drive "old" with network unplugged 44.120
Then the boot device has safe access rights 1.846
And Tails is running from USB drive "old" 0.210
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.142
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.748
After features/support/hooks.rb:108 0.026
Tags: @product
1:21.571
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 47.641
Then Tails is running from USB drive "old" 0.176
And I create a persistent partition 23.053
And I take note of which tps features are available 6.037
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 4.077
After features/support/hooks.rb:339 0.270
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.866
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.320
Then Tails is running from USB drive "old" 0.171
And all tps features are active 6.887
When I write some files expected to persist 1.185
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.298
And all persistent directories from the old Tails version have safe access rights 1.693
And I take note of which tps features are available 5.793
And I shutdown Tails and wait for the computer to power off 4.066
# 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.122
After features/support/hooks.rb:339 0.402
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.497
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.298
And I log in to a new session 12.036
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.628
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.252
Then the running Tails is installed on USB drive "to_upgrade" 16.773
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.117
After features/support/hooks.rb:339 2.198
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.073
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.169
Then all tps features from the old Tails version are active 1.103
And Tails is running from USB drive "to_upgrade" 0.187
And the boot device has safe access rights 1.779
And the expected persistent files created with the old Tails version are present in the filesystem 0.987
And all persistent directories from the old Tails version have safe access rights 1.765
After features/support/hooks.rb:339 0.590
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:40.963
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.057
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.168
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.222
When the network is plugged 0.037
And Tor is ready 13.068
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.119
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.323
Given I shutdown Tails and wait for the computer to power off 6.484
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.036
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.626
And the file system changes introduced in version 6.2~testoverlayfs are present 0.167
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.159
When the network is plugged 0.038
And Tor is ready 9.976
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.469
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.037
Given I shutdown Tails and wait for the computer to power off 4.134
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.181
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.600
And the file system changes introduced in version 6.3~testoverlayfs are present 0.301
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.095
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.149
When the network is plugged 0.033
And Tor is ready 10.162
Then the Upgrader considers the system as up-to-date 10.410
# 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.041
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.325
After features/support/hooks.rb:339 0.889
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.531
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.844
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.171
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.032
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 8.200
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.214
After features/support/hooks.rb:339 0.772
After features/support/hooks.rb:108 0.000