Project Number Date
test_Tails_ISO_stable 6224 23 Mar 2026, 20:09

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 14:11.857 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:41.290
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 15.447
When I start Tails from USB drive "old" with network unplugged 1:21.118
Then the boot device has safe access rights 2.954
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 1.593
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.123
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 57.669
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 25.529
And I take note of which tps features are available 0.842
Then a Tails persistence partition exists on USB drive "old" 0.736
And I shutdown Tails and wait for the computer to power off 7.039
After features/support/hooks.rb:331 0.205
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.509
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.880
Then Tails is running from USB drive "old" 0.239
And all tps features are active 1.125
When I write some files expected to persist 1.370
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.538
And all persistent directories from the old Tails version have safe access rights 2.196
And I take note of which tps features are available 0.171
And I shutdown Tails and wait for the computer to power off 8.828
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.883
After features/support/hooks.rb:331 0.397
After features/support/hooks.rb:100 0.006
Tags: @product
2:26.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.672
And I log in to a new session 19.054
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.944
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.497
Then the running Tails is installed on USB drive "to_upgrade" 18.918
And I unplug USB drive "to_upgrade" 0.168
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:331 5.242
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.130
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.474
Then all tps features from the old Tails version are active 1.232
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 2.684
And the expected persistent files created with the old Tails version are present in the filesystem 1.365
And all persistent directories from the old Tails version have safe access rights 2.003
After features/support/hooks.rb:331 0.737
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
4:54.162
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
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.184
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.502
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.016
And Tor is ready 27.371
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.399
Given I shutdown Tails and wait for the computer to power off 21.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.703
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.161
# 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.260
When the network is plugged 0.016
And Tor is ready 22.501
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.413
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.942
Given I shutdown Tails and wait for the computer to power off 13.872
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.859
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.165
And the file system changes introduced in version 6.3~testoverlayfs are present 0.350
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.015
And Tor is ready 22.126
Then the Upgrader considers the system as up-to-date 0.128
# 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.931
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.380
After features/support/hooks.rb:331 1.013
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
49.992
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 7.833
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 41.431
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.393
After features/support/hooks.rb:331 0.730
After features/support/hooks.rb:100 0.000