Project Number Date
test_Tails_ISO_devel 4672 12 Oct 2026, 15:58

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:30.132 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
54.413
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.156
When I start Tails from USB drive "old" with network unplugged 37.892
Then the boot device has safe access rights 1.748
And Tails is running from USB drive "old" 0.188
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.028
And udev-watchdog is monitoring the correct device 0.125
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.633
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.212
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 45.071
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 22.072
And I take note of which tps features are available 6.356
Then a Tails persistence partition exists on USB drive "old" 0.506
And I shutdown Tails and wait for the computer to power off 3.906
After features/support/hooks.rb:339 0.633
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.036
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 56.814
Then Tails is running from USB drive "old" 0.182
And all tps features are active 6.560
When I write some files expected to persist 1.252
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.139
And all persistence configuration files have safe access rights 0.250
And all persistent directories from the old Tails version have safe access rights 1.687
And I take note of which tps features are available 6.308
And I shutdown Tails and wait for the computer to power off 2.545
# 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.180
After features/support/hooks.rb:339 0.246
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.800
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 7.962
And I log in to a new session 10.065
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.620
And I plug USB drive "to_upgrade" 2.575
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.730
Then the running Tails is installed on USB drive "to_upgrade" 17.607
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.571
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.210
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.479
Then all tps features from the old Tails version are active 0.963
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.032
And the expected persistent files created with the old Tails version are present in the filesystem 0.891
And all persistent directories from the old Tails version have safe access rights 1.554
After features/support/hooks.rb:339 0.947
After features/support/hooks.rb:108 0.005
3:18.846
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.131
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
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.288
When the network is plugged 0.033
And Tor is ready 12.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.322
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.629
Given I shutdown Tails and wait for the computer to power off 6.448
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.565
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.381
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.187
# 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.173
When the network is plugged 0.033
And Tor is ready 10.157
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 3.368
Given I shutdown Tails and wait for the computer to power off 3.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 57.832
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.470
And the file system changes introduced in version 6.3~testoverlayfs are present 0.331
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.026
And Tor is ready 9.980
Then the Upgrader considers the system as up-to-date 0.075
# 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.014
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:339 1.005
After features/support/hooks.rb:108 0.009
17.613
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.841
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.288
After features/support/hooks.rb:339 0.549
After features/support/hooks.rb:108 0.000