Project Number Date
test_Tails_ISO_devel 4392 12 May 2026, 13:23

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:19.574 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.912
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.024
When I start Tails from USB drive "old" with network unplugged 43.425
Then the boot device has safe access rights 2.711
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:335 1.279
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.931
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 54.729
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 24.296
And I take note of which tps features are available 0.972
Then a Tails persistence partition exists on USB drive "old" 0.543
And I shutdown Tails and wait for the computer to power off 7.039
After features/support/hooks.rb:335 0.414
After features/support/hooks.rb:104 0.008
Tags: @product
1:25.124
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.975
Then Tails is running from USB drive "old" 0.268
And all tps features are active 1.232
When I write some files expected to persist 1.363
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.461
And all persistent directories from the old Tails version have safe access rights 1.824
And I take note of which tps features are available 0.174
And I shutdown Tails and wait for the computer to power off 4.058
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.458
After features/support/hooks.rb:335 0.244
After features/support/hooks.rb:104 0.007
Tags: @product
2:11.710
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.843
And I log in to a new session 12.993
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.724
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.872
Then the running Tails is installed on USB drive "to_upgrade" 15.734
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:335 6.746
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.528
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.507
Then all tps features from the old Tails version are active 1.006
And Tails is running from USB drive "to_upgrade" 0.254
And the boot device has safe access rights 2.468
And the expected persistent files created with the old Tails version are present in the filesystem 1.134
And all persistent directories from the old Tails version have safe access rights 2.102
After features/support/hooks.rb:335 0.735
After features/support/hooks.rb:104 0.008
4:35.892
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.667
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.015
And Tor is ready 21.063
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.463
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.493
Given I shutdown Tails and wait for the computer to power off 20.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.744
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.169
And the file system changes introduced in version 6.2~testoverlayfs are present 0.227
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.169
# 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.195
When the network is plugged 0.012
And Tor is ready 20.644
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.376
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.434
Given I shutdown Tails and wait for the computer to power off 12.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.863
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.379
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.190
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.016
And Tor is ready 20.944
Then the Upgrader considers the system as up-to-date 0.095
# 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.145
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.428
After features/support/hooks.rb:335 1.087
After features/support/hooks.rb:104 0.014
26.475
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.528
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 18.173
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.398
After features/support/hooks.rb:335 0.842
After features/support/hooks.rb:104 0.000