Project Number Date
test_Tails_ISO_devel 4604 08 Sep 2026, 18: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:50.209 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:15.841
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.766
When I start Tails from USB drive "old" with network unplugged 57.561
Then the boot device has safe access rights 2.587
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.265
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 1.255
After features/support/hooks.rb:108 0.008
Tags: @product
1:28.833
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 50.342
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 25.446
And I take note of which tps features are available 7.855
Then a Tails persistence partition exists on USB drive "old" 0.648
And I shutdown Tails and wait for the computer to power off 4.043
After features/support/hooks.rb:339 0.563
After features/support/hooks.rb:108 0.005
Tags: @product
1:37.779
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.556
Then Tails is running from USB drive "old" 0.298
And all tps features are active 8.392
When I write some files expected to persist 1.359
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.233
And all persistent directories from the old Tails version have safe access rights 1.694
And I take note of which tps features are available 6.357
And I shutdown Tails and wait for the computer to power off 2.812
# 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.788
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.007
Tags: @product
2:15.137
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 9.443
And I log in to a new session 11.658
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.998
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.654
Then the running Tails is installed on USB drive "to_upgrade" 18.934
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.676
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.017
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.726
Then all tps features from the old Tails version are active 1.148
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.504
And the expected persistent files created with the old Tails version are present in the filesystem 1.219
And all persistent directories from the old Tails version have safe access rights 2.118
After features/support/hooks.rb:339 0.693
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
3:40.793
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 with a persistent partition enabled and logged in 8.432
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.268
When the network is plugged 0.027
And Tor is ready 13.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.303
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.239
Given I shutdown Tails and wait for the computer to power off 5.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.506
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.441
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.193
When the network is plugged 0.709
And Tor is ready 10.531
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.001
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.579
Given I shutdown Tails and wait for the computer to power off 3.934
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.087
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.333
And the file system changes introduced in version 6.3~testoverlayfs are present 0.377
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.039
And Tor is ready 10.527
Then the Upgrader considers the system as up-to-date 0.083
# 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.741
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:339 0.628
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.807
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 with a persistent partition enabled and logged in 8.345
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 9.993
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.047
After features/support/hooks.rb:339 0.984
After features/support/hooks.rb:108 0.000