Project Number Date
test_Tails_ISO_devel 4237 17 Feb 2026, 14:28

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.652 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:16.753
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.747
When I start Tails from USB drive "old" with network unplugged 56.450
Then the boot device has safe access rights 3.699
And Tails is running from USB drive "old" 0.265
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.249
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 1.418
After features/support/hooks.rb:100 0.011
Tags: @product
1:35.846
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.109
And I start Tails from USB drive "old" with network unplugged and I login 1:0.027
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 26.504
And I take note of which tps features are available 1.007
Then a Tails persistence partition exists on USB drive "old" 0.886
And I shutdown Tails and wait for the computer to power off 7.083
After features/support/hooks.rb:331 0.580
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.761
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.005
Then Tails is running from USB drive "old" 0.256
And all tps features are active 1.273
When I write some files expected to persist 1.751
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.302
And all persistence configuration files have safe access rights 0.527
And all persistent directories from the old Tails version have safe access rights 2.624
And I take note of which tps features are available 0.289
And I shutdown Tails and wait for the computer to power off 4.686
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.990
After features/support/hooks.rb:331 0.206
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.435
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.636
And I log in to a new session 12.124
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.208
And I plug USB drive "to_upgrade" 2.304
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.693
Then the running Tails is installed on USB drive "to_upgrade" 16.760
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.442
After features/support/hooks.rb:331 3.134
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.708
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.134
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.754
Then all tps features from the old Tails version are active 0.954
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 2.764
And the expected persistent files created with the old Tails version are present in the filesystem 1.145
And all persistent directories from the old Tails version have safe access rights 2.686
After features/support/hooks.rb:331 0.738
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
3:56.044
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 with a persistent partition enabled and logged in 8.976
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.021
And Tor is ready 13.648
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.439
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.635
Given I shutdown Tails and wait for the computer to power off 7.086
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.694
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.208
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.204
When the network is plugged 0.012
And Tor is ready 11.718
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.079
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.627
Given I shutdown Tails and wait for the computer to power off 8.277
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.035
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.326
And the file system changes introduced in version 6.3~testoverlayfs are present 0.420
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.015
And Tor is ready 11.189
Then the Upgrader considers the system as up-to-date 10.641
# 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.456
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:331 1.176
After features/support/hooks.rb:100 0.044
Tags: @product @automatic_upgrade
21.102
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.664
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 9.601
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.368
After features/support/hooks.rb:331 0.740
After features/support/hooks.rb:100 0.000