Project Number Date
test_Tails_ISO_devel 4261 02 Mar 2026, 07:52

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:22.306 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:6.356
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.959
When I start Tails from USB drive "old" with network unplugged 47.958
Then the boot device has safe access rights 2.568
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.233
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:331 1.215
After features/support/hooks.rb:100 0.005
Tags: @product
1:27.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 53.636
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 23.890
And I take note of which tps features are available 0.717
Then a Tails persistence partition exists on USB drive "old" 0.644
And I shutdown Tails and wait for the computer to power off 8.130
After features/support/hooks.rb:331 0.388
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.808
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.728
Then Tails is running from USB drive "old" 0.239
And all tps features are active 1.294
When I write some files expected to persist 1.253
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.424
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 4.075
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.974
After features/support/hooks.rb:331 0.481
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.424
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.326
And I log in to a new session 9.968
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.060
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.137
Then the running Tails is installed on USB drive "to_upgrade" 16.434
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:331 2.056
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.249
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.023
Then all tps features from the old Tails version are active 0.945
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 2.665
And the expected persistent files created with the old Tails version are present in the filesystem 1.131
And all persistent directories from the old Tails version have safe access rights 2.164
After features/support/hooks.rb:331 0.594
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:38.239
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 with a persistent partition enabled and logged in 8.355
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.305
When the network is plugged 0.012
And Tor is ready 20.079
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.363
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.436
Given I shutdown Tails and wait for the computer to power off 20.044
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.723
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.139
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.251
When the network is plugged 0.013
And Tor is ready 20.640
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.360
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.987
Given I shutdown Tails and wait for the computer to power off 17.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.911
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.088
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.014
And Tor is ready 22.047
Then the Upgrader considers the system as up-to-date 0.109
# 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.546
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.557
After features/support/hooks.rb:331 0.764
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
24.767
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.720
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
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.016
And Tor is ready 16.346
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.352
After features/support/hooks.rb:331 1.163
After features/support/hooks.rb:100 0.000