Project Number Date
test_Tails_ISO_devel 4513 25 Jul 2026, 11:26

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:59.477 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.451
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.206
When I start Tails from USB drive "old" with network unplugged 43.408
Then the boot device has safe access rights 2.928
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.240
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:339 3.738
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.245
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 56.777
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 25.071
And I take note of which tps features are available 4.430
Then a Tails persistence partition exists on USB drive "old" 0.564
And I shutdown Tails and wait for the computer to power off 4.037
After features/support/hooks.rb:339 0.151
After features/support/hooks.rb:108 0.007
Tags: @product
1:38.483
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.417
Then Tails is running from USB drive "old" 0.233
And all tps features are active 6.205
When I write some files expected to persist 1.742
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.076
And I take note of which tps features are available 4.227
And I shutdown Tails and wait for the computer to power off 4.176
# 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" 12.786
After features/support/hooks.rb:339 0.454
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.452
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 without a persistent partition and stopped at Tails Greeter's login screen 7.911
And I log in to a new session 13.067
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.962
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.171
Then the running Tails is installed on USB drive "to_upgrade" 16.832
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:339 2.278
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.149
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.725
Then all tps features from the old Tails version are active 0.930
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 3.044
And the expected persistent files created with the old Tails version are present in the filesystem 1.202
And all persistent directories from the old Tails version have safe access rights 1.949
After features/support/hooks.rb:339 0.573
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:58.176
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.356
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.018
And Tor is ready 13.174
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.228
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.536
Given I shutdown Tails and wait for the computer to power off 7.084
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.967
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 5.679
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.169
# 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.253
When the network is plugged 0.015
And Tor is ready 9.907
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.159
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.532
Given I shutdown Tails and wait for the computer to power off 4.670
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.759
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.206
And the file system changes introduced in version 6.3~testoverlayfs are present 0.332
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.014
And Tor is ready 11.295
Then the Upgrader considers the system as up-to-date 10.615
# 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 4.936
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.422
After features/support/hooks.rb:339 0.852
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.518
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.782
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 11.427
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.969
After features/support/hooks.rb:339 0.752
After features/support/hooks.rb:108 0.000