Project Number Date
test_Tails_ISO_stable 6124 06 Feb 2026, 07:05

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 10:58.469 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:14.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.302
When I start Tails from USB drive "old" with network unplugged 56.707
Then the boot device has safe access rights 2.390
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 3.415
After features/support/hooks.rb:100 0.052
Tags: @product
1:25.619
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.044
And I start Tails from USB drive "old" with network unplugged and I login 52.424
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 23.598
And I take note of which tps features are available 0.719
Then a Tails persistence partition exists on USB drive "old" 0.495
And I shutdown Tails and wait for the computer to power off 8.077
After features/support/hooks.rb:331 0.227
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.844
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.385
Then Tails is running from USB drive "old" 0.238
And all tps features are active 1.072
When I write some files expected to persist 1.209
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.264
And all persistent directories from the old Tails version have safe access rights 1.726
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 7.904
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.672
After features/support/hooks.rb:331 0.512
After features/support/hooks.rb:100 0.006
Tags: @product
2:8.517
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 without a persistent partition and stopped at Tails Greeter's login screen 8.626
And I log in to a new session 9.149
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.884
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.213
Then the running Tails is installed on USB drive "to_upgrade" 15.155
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:331 2.337
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.403
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.238
Then all tps features from the old Tails version are active 0.917
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.219
And the expected persistent files created with the old Tails version are present in the filesystem 1.004
And all persistent directories from the old Tails version have safe access rights 1.738
After features/support/hooks.rb:331 0.848
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:23.163
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.127
And no SquashFS delta is installed 0.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.014
And Tor is ready 13.038
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.711
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.895
Given I shutdown Tails and wait for the computer to power off 9.201
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.846
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 0.983
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.187
When the network is plugged 0.013
And Tor is ready 10.517
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.768
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.634
Given I shutdown Tails and wait for the computer to power off 2.691
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.233
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.003
And the file system changes introduced in version 6.3~testoverlayfs are present 0.333
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.013
And Tor is ready 10.683
Then the Upgrader considers the system as up-to-date 10.563
# 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 3.718
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.361
After features/support/hooks.rb:331 0.781
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
18.777
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.482
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.265
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.679
After features/support/hooks.rb:331 0.983
After features/support/hooks.rb:100 0.000