Project Number Date
test_Tails_ISO_devel 4228 11 Feb 2026, 20:46

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:26.897 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:17.120
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 14.710
When I start Tails from USB drive "old" with network unplugged 57.314
Then the boot device has safe access rights 3.073
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.254
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:331 3.529
After features/support/hooks.rb:100 0.029
Tags: @product
1:32.561
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.117
And I start Tails from USB drive "old" with network unplugged and I login 59.818
Then Tails is running from USB drive "old" 0.415
And I create a persistent partition 26.239
And I take note of which tps features are available 0.913
Then a Tails persistence partition exists on USB drive "old" 0.619
And I shutdown Tails and wait for the computer to power off 4.437
After features/support/hooks.rb:331 0.398
After features/support/hooks.rb:100 0.008
Tags: @product
1:35.355
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.675
Then Tails is running from USB drive "old" 0.275
And all tps features are active 1.646
When I write some files expected to persist 1.598
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.290
And I take note of which tps features are available 0.198
And I shutdown Tails and wait for the computer to power off 4.172
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.814
After features/support/hooks.rb:331 0.556
After features/support/hooks.rb:100 0.006
Tags: @product
2:18.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.584
And I log in to a new session 12.813
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.775
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.131
Then the running Tails is installed on USB drive "to_upgrade" 18.407
And I unplug USB drive "to_upgrade" 0.171
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:331 2.378
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.618
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.939
Then all tps features from the old Tails version are active 1.316
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.161
And the expected persistent files created with the old Tails version are present in the filesystem 1.413
And all persistent directories from the old Tails version have safe access rights 2.402
After features/support/hooks.rb:331 0.685
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:1.187
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.795
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.542
When the network is plugged 0.018
And Tor is ready 13.250
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.028
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.330
Given I shutdown Tails and wait for the computer to power off 11.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.160
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.640
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.311
When the network is plugged 0.035
And Tor is ready 10.776
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.393
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.599
Given I shutdown Tails and wait for the computer to power off 4.224
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.135
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.596
And the file system changes introduced in version 6.3~testoverlayfs are present 0.539
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.224
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.047
And Tor is ready 10.552
Then the Upgrader considers the system as up-to-date 10.827
# 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.865
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.420
After features/support/hooks.rb:331 0.827
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
22.704
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.594
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.099
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 11.234
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.446
After features/support/hooks.rb:331 1.117
After features/support/hooks.rb:100 0.000