Project Number Date
test_Tails_ISO_stable 6596 19 Aug 2026, 13:30

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:20.123 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:1.773
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.265
When I start Tails from USB drive "old" with network unplugged 45.022
Then the boot device has safe access rights 1.803
And Tails is running from USB drive "old" 0.166
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.155
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 3.767
After features/support/hooks.rb:108 0.044
Tags: @product
1:21.017
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 48.270
Then Tails is running from USB drive "old" 0.253
And I create a persistent partition 22.041
And I take note of which tps features are available 5.953
Then a Tails persistence partition exists on USB drive "old" 0.458
And I shutdown Tails and wait for the computer to power off 3.948
After features/support/hooks.rb:339 0.391
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.501
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.661
Then Tails is running from USB drive "old" 0.225
And all tps features are active 7.142
When I write some files expected to persist 1.035
# 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.282
And all persistent directories from the old Tails version have safe access rights 1.487
And I take note of which tps features are available 5.505
And I shutdown Tails and wait for the computer to power off 2.552
# 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.326
After features/support/hooks.rb:339 0.306
After features/support/hooks.rb:108 0.006
Tags: @product
2:24.707
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 21.427
And I log in to a new session 11.305
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.596
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.837
Then the running Tails is installed on USB drive "to_upgrade" 18.094
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 6.894
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.601
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:2.783
Then all tps features from the old Tails version are active 1.227
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.414
And the expected persistent files created with the old Tails version are present in the filesystem 1.030
And all persistent directories from the old Tails version have safe access rights 1.830
After features/support/hooks.rb:339 0.598
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:33.306
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.397
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
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.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.038
And Tor is ready 13.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.326
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.353
Given I shutdown Tails and wait for the computer to power off 5.458
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.267
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.741
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.179
When the network is plugged 0.037
And Tor is ready 10.325
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.507
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.699
Given I shutdown Tails and wait for the computer to power off 4.112
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.547
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.329
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.088
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.162
When the network is plugged 0.027
And Tor is ready 10.581
Then the Upgrader considers the system as up-to-date 0.092
# 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.521
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.354
After features/support/hooks.rb:339 1.190
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.215
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 8.338
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 9.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.506
After features/support/hooks.rb:339 1.013
After features/support/hooks.rb:108 0.000