Project Number Date
test_Tails_ISO_devel 4381 07 May 2026, 11:02

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:52.195 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
58.380
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.195
When I start Tails from USB drive "old" with network unplugged 40.899
Then the boot device has safe access rights 2.592
And Tails is running from USB drive "old" 0.205
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:331 3.710
After features/support/hooks.rb:100 0.006
Tags: @product
1:20.025
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 52.988
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 22.936
And I take note of which tps features are available 0.672
Then a Tails persistence partition exists on USB drive "old" 0.481
And I shutdown Tails and wait for the computer to power off 2.656
After features/support/hooks.rb:331 0.310
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.733
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.998
Then Tails is running from USB drive "old" 0.218
And all tps features are active 1.130
When I write some files expected to persist 1.245
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.161
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 1.851
And I take note of which tps features are available 0.138
And I shutdown Tails and wait for the computer to power off 7.929
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.631
After features/support/hooks.rb:331 0.564
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.625
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 7.738
And I log in to a new session 11.123
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.728
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.081
Then the running Tails is installed on USB drive "to_upgrade" 15.429
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 2.001
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.165
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.450
Then all tps features from the old Tails version are active 0.934
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.483
And the expected persistent files created with the old Tails version are present in the filesystem 1.102
And all persistent directories from the old Tails version have safe access rights 1.916
After features/support/hooks.rb:331 0.573
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
4:29.028
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.493
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.018
And Tor is ready 19.674
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.401
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.216
Given I shutdown Tails and wait for the computer to power off 20.176
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.355
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.109
And the file system changes introduced in version 6.2~testoverlayfs are present 0.251
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# 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.196
When the network is plugged 0.016
And Tor is ready 21.282
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.347
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.782
Given I shutdown Tails and wait for the computer to power off 17.085
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.617
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.107
And the file system changes introduced in version 6.3~testoverlayfs are present 0.363
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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.013
And Tor is ready 21.162
Then the Upgrader considers the system as up-to-date 0.133
# 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.230
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.402
After features/support/hooks.rb:331 0.902
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
24.236
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.253
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 16.273
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.359
After features/support/hooks.rb:331 0.966
After features/support/hooks.rb:100 0.000