Project Number Date
test_Tails_ISO_devel 4298 27 Mar 2026, 18:17

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:54.510 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:12.906
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.744
When I start Tails from USB drive "old" with network unplugged 54.486
Then the boot device has safe access rights 2.840
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.251
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:331 1.308
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.286
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 54.415
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 24.698
And I take note of which tps features are available 0.693
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 8.524
After features/support/hooks.rb:331 0.656
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.758
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.722
Then Tails is running from USB drive "old" 0.306
And all tps features are active 1.163
When I write some files expected to persist 1.395
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.586
And all persistent directories from the old Tails version have safe access rights 2.177
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 4.233
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.764
After features/support/hooks.rb:331 0.098
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.992
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.297
And I log in to a new session 12.696
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.984
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.103
Then the running Tails is installed on USB drive "to_upgrade" 15.367
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:331 2.232
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.606
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.376
Then all tps features from the old Tails version are active 1.224
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.693
And the expected persistent files created with the old Tails version are present in the filesystem 1.254
And all persistent directories from the old Tails version have safe access rights 1.783
After features/support/hooks.rb:331 0.628
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
4:59.806
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 8.646
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.390
When the network is plugged 0.020
And Tor is ready 21.839
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.378
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.450
Given I shutdown Tails and wait for the computer to power off 20.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.457
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.269
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.184
When the network is plugged 0.017
And Tor is ready 39.271
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.406
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.146
Given I shutdown Tails and wait for the computer to power off 17.499
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.634
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.351
And the file system changes introduced in version 6.3~testoverlayfs are present 0.403
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.177
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.034
And Tor is ready 21.026
Then the Upgrader considers the system as up-to-date 0.087
# 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.175
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.353
After features/support/hooks.rb:331 0.628
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
24.153
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.518
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 15.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.390
After features/support/hooks.rb:331 0.605
After features/support/hooks.rb:100 0.000