Project Number Date
test_Tails_ISO_devel 4655 03 Oct 2026, 11:07

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:44.613 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:0.973
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.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.208
When I start Tails from USB drive "old" with network unplugged 44.408
Then the boot device has safe access rights 1.682
And Tails is running from USB drive "old" 0.170
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 3.549
After features/support/hooks.rb:108 0.034
Tags: @product
1:19.740
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 46.401
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 22.600
And I take note of which tps features are available 6.076
Then a Tails persistence partition exists on USB drive "old" 0.461
And I shutdown Tails and wait for the computer to power off 3.861
After features/support/hooks.rb:339 0.591
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.860
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.971
Then Tails is running from USB drive "old" 0.187
And all tps features are active 7.444
When I write some files expected to persist 1.039
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.124
And all persistence configuration files have safe access rights 0.290
And all persistent directories from the old Tails version have safe access rights 1.666
And I take note of which tps features are available 5.825
And I shutdown Tails and wait for the computer to power off 4.123
# 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.089
After features/support/hooks.rb:339 0.413
After features/support/hooks.rb:108 0.011
Tags: @product
2:10.235
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.851
And I log in to a new session 11.546
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.588
And I plug USB drive "to_upgrade" 2.188
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.742
Then the running Tails is installed on USB drive "to_upgrade" 17.098
And I unplug USB drive "to_upgrade" 0.111
And I unplug USB drive "__internal" 0.107
After features/support/hooks.rb:339 0.599
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.335
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.674
Then all tps features from the old Tails version are active 1.021
And Tails is running from USB drive "to_upgrade" 0.154
And the boot device has safe access rights 2.089
And the expected persistent files created with the old Tails version are present in the filesystem 0.936
And all persistent directories from the old Tails version have safe access rights 1.380
After features/support/hooks.rb:339 0.828
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:20.005
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.022
And no SquashFS delta is installed 0.116
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.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.239
When the network is plugged 0.024
And Tor is ready 12.183
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.904
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.226
Given I shutdown Tails and wait for the computer to power off 5.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.123
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.369
And the file system changes introduced in version 6.2~testoverlayfs are present 0.144
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.107
# 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.152
When the network is plugged 0.034
And Tor is ready 10.820
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.287
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.624
Given I shutdown Tails and wait for the computer to power off 2.552
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.429
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.315
And the file system changes introduced in version 6.3~testoverlayfs are present 0.281
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.033
And Tor is ready 10.318
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.101
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.293
After features/support/hooks.rb:339 0.836
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
17.463
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.684
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 8.010
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.436
After features/support/hooks.rb:339 0.690
After features/support/hooks.rb:108 0.000