Project Number Date
test_Tails_ISO_devel 4640 28 Sep 2026, 16:28

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:26.917 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:6.190
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.115
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.322
When I start Tails from USB drive "old" with network unplugged 48.851
Then the boot device has safe access rights 2.219
And Tails is running from USB drive "old" 0.192
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.822
After features/support/hooks.rb:108 0.014
Tags: @product
1:21.217
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 "old" with network unplugged and I login 47.683
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 23.501
And I take note of which tps features are available 6.647
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 2.569
After features/support/hooks.rb:339 0.097
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.769
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.683
Then Tails is running from USB drive "old" 0.223
And all tps features are active 7.525
When I write some files expected to persist 1.091
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.269
And all persistent directories from the old Tails version have safe access rights 1.647
And I take note of which tps features are available 6.015
And I shutdown Tails and wait for the computer to power off 5.157
# 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.893
After features/support/hooks.rb:339 0.571
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.195
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.424
And I log in to a new session 11.736
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.650
And I plug USB drive "to_upgrade" 2.278
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.923
Then the running Tails is installed on USB drive "to_upgrade" 18.905
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 2.157
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.792
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.097
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.527
Then all tps features from the old Tails version are active 0.991
And Tails is running from USB drive "to_upgrade" 0.192
And the boot device has safe access rights 2.051
And the expected persistent files created with the old Tails version are present in the filesystem 1.033
And all persistent directories from the old Tails version have safe access rights 1.899
After features/support/hooks.rb:339 0.874
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
3:40.300
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.721
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.031
And Tor is ready 12.688
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.766
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.932
Given I shutdown Tails and wait for the computer to power off 5.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.505
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.976
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.104
# 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.214
When the network is plugged 0.028
And Tor is ready 10.577
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.321
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.135
Given I shutdown Tails and wait for the computer to power off 2.610
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.138
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.511
And the file system changes introduced in version 6.3~testoverlayfs are present 0.362
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.029
And Tor is ready 10.710
Then the Upgrader considers the system as up-to-date 0.100
# 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.265
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.367
After features/support/hooks.rb:339 1.034
After features/support/hooks.rb:108 0.050
Tags: @product @automatic_upgrade
18.450
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 with a persistent partition enabled and logged in 8.373
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 8.191
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.563
After features/support/hooks.rb:339 0.696
After features/support/hooks.rb:108 0.000