Project Number Date
test_Tails_ISO_stable 6040 06 Jan 2026, 12:11

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 13:11.912 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:23.946
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.159
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.202
When I start Tails from USB drive "old" with network unplugged 50.346
Then the boot device has safe access rights 3.325
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:331 3.817
After features/support/hooks.rb:100 0.012
Tags: @product
1:41.735
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:2.053
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 29.136
And I take note of which tps features are available 1.201
Then a Tails persistence partition exists on USB drive "old" 0.853
And I shutdown Tails and wait for the computer to power off 7.939
After features/support/hooks.rb:331 0.210
After features/support/hooks.rb:100 0.009
Tags: @product
1:46.797
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:13.840
Then Tails is running from USB drive "old" 0.375
And all tps features are active 2.075
When I write some files expected to persist 1.652
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.294
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 7.564
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.693
After features/support/hooks.rb:331 0.629
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.556
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.214
And I log in to a new session 9.225
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.061
And I plug USB drive "to_upgrade" 2.797
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.932
Then the running Tails is installed on USB drive "to_upgrade" 17.849
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.261
After features/support/hooks.rb:331 3.814
After features/support/hooks.rb:100 0.000
Tags: @product
1:22.202
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.896
Then all tps features from the old Tails version are active 1.762
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.272
And the expected persistent files created with the old Tails version are present in the filesystem 1.674
And all persistent directories from the old Tails version have safe access rights 2.131
After features/support/hooks.rb:331 2.822
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:6.227
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 12.701
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.060
And Tor is ready 12.845
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.873
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.644
Given I shutdown Tails and wait for the computer to power off 7.517
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.400
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.091
And the file system changes introduced in version 6.2~testoverlayfs are present 0.261
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.232
When the network is plugged 0.055
And Tor is ready 12.559
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.604
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.501
Given I shutdown Tails and wait for the computer to power off 8.215
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.697
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.498
And the file system changes introduced in version 6.3~testoverlayfs are present 0.451
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.195
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.057
And Tor is ready 12.372
Then the Upgrader considers the system as up-to-date 0.168
# 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 6.079
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.590
After features/support/hooks.rb:331 1.021
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
20.445
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 9.288
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 10.118
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.631
After features/support/hooks.rb:331 1.015
After features/support/hooks.rb:100 0.000