Project Number Date
test_Tails_ISO_devel 4558 18 Aug 2026, 19:14

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 12:33.103 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:23.741
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.124
And I create a 7200 MiB disk named "old" 0.034
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 16.328
When I start Tails from USB drive "old" with network unplugged 1:2.326
Then the boot device has safe access rights 3.121
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.936
After features/support/hooks.rb:108 0.009
Tags: @product
1:31.076
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.125
And I start Tails from USB drive "old" with network unplugged and I login 51.472
Then Tails is running from USB drive "old" 0.193
And I create a persistent partition 26.337
And I take note of which tps features are available 7.192
Then a Tails persistence partition exists on USB drive "old" 0.513
And I shutdown Tails and wait for the computer to power off 5.240
After features/support/hooks.rb:339 0.353
After features/support/hooks.rb:108 0.006
Tags: @product
1:42.762
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.342
Then Tails is running from USB drive "old" 0.214
And all tps features are active 9.380
When I write some files expected to persist 1.229
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.370
And all persistent directories from the old Tails version have safe access rights 1.905
And I take note of which tps features are available 7.417
And I shutdown Tails and wait for the computer to power off 4.287
# 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.334
After features/support/hooks.rb:339 0.610
After features/support/hooks.rb:108 0.007
Tags: @product
2:19.167
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.000
And I log in to a new session 13.087
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.059
And I plug USB drive "to_upgrade" 2.269
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.867
Then the running Tails is installed on USB drive "to_upgrade" 18.821
And I unplug USB drive "to_upgrade" 0.289
And I unplug USB drive "__internal" 0.771
After features/support/hooks.rb:339 3.399
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.858
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.105
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.106
Then all tps features from the old Tails version are active 1.135
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.388
And the expected persistent files created with the old Tails version are present in the filesystem 1.015
And all persistent directories from the old Tails version have safe access rights 1.881
After features/support/hooks.rb:339 0.898
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
4:3.037
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 22.083
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
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.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.029
And Tor is ready 13.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.337
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.296
Given I shutdown Tails and wait for the computer to power off 7.131
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.063
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.718
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.148
When the network is plugged 0.034
And Tor is ready 10.404
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.605
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.145
Given I shutdown Tails and wait for the computer to power off 3.993
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.842
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.189
And the file system changes introduced in version 6.3~testoverlayfs are present 0.422
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.025
And Tor is ready 12.414
Then the Upgrader considers the system as up-to-date 0.125
# 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.018
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.369
After features/support/hooks.rb:339 0.860
After features/support/hooks.rb:108 0.066
Tags: @product @automatic_upgrade
20.458
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.267
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 9.634
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.151
After features/support/hooks.rb:339 0.725
After features/support/hooks.rb:108 0.000