Project Number Date
test_Tails_ISO_stable 6147 14 Feb 2026, 11:45

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:12.560 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:23.339
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.211
When I start Tails from USB drive "old" with network unplugged 1:4.501
Then the boot device has safe access rights 2.842
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 4.027
After features/support/hooks.rb:100 0.020
Tags: @product
1:29.895
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 55.619
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 25.559
And I take note of which tps features are available 0.850
Then a Tails persistence partition exists on USB drive "old" 0.572
And I shutdown Tails and wait for the computer to power off 6.993
After features/support/hooks.rb:331 0.498
After features/support/hooks.rb:100 0.007
Tags: @product
1:36.928
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.587
Then Tails is running from USB drive "old" 0.444
And all tps features are active 2.006
When I write some files expected to persist 1.539
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.279
And all persistent directories from the old Tails version have safe access rights 2.211
And I take note of which tps features are available 0.227
And I shutdown Tails and wait for the computer to power off 8.078
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.245
After features/support/hooks.rb:331 0.431
After features/support/hooks.rb:100 0.007
Tags: @product
2:15.258
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.733
And I log in to a new session 12.734
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.827
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.738
Then the running Tails is installed on USB drive "to_upgrade" 16.691
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:331 2.726
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.885
Then all tps features from the old Tails version are active 0.931
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.801
And the expected persistent files created with the old Tails version are present in the filesystem 1.228
And all persistent directories from the old Tails version have safe access rights 2.248
After features/support/hooks.rb:331 0.911
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:53.246
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.673
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
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.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.343
When the network is plugged 0.013
And Tor is ready 13.587
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.743
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.492
Given I shutdown Tails and wait for the computer to power off 9.914
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.152
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.153
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# 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.213
When the network is plugged 0.017
And Tor is ready 11.131
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.718
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.812
Given I shutdown Tails and wait for the computer to power off 8.005
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.542
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.291
And the file system changes introduced in version 6.3~testoverlayfs are present 0.561
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.168
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.015
And Tor is ready 11.238
Then the Upgrader considers the system as up-to-date 10.647
# 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.054
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.409
After features/support/hooks.rb:331 0.785
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
21.479
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 7.809
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
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.019
And Tor is ready 10.113
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.246
After features/support/hooks.rb:331 0.700
After features/support/hooks.rb:100 0.000