Project Number Date
test_Tails_ISO_devel 4258 27 Feb 2026, 11:19

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 11:59.207 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:6.207
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.104
When I start Tails from USB drive "old" with network unplugged 48.859
Then the boot device has safe access rights 2.483
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 1.200
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.405
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 50.828
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 23.196
And I take note of which tps features are available 0.680
Then a Tails persistence partition exists on USB drive "old" 0.536
And I shutdown Tails and wait for the computer to power off 7.869
After features/support/hooks.rb:331 0.456
After features/support/hooks.rb:100 0.007
Tags: @product
1:18.828
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.163
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.121
When I write some files expected to persist 1.278
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.466
And all persistent directories from the old Tails version have safe access rights 1.815
And I take note of which tps features are available 0.187
And I shutdown Tails and wait for the computer to power off 2.705
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.556
After features/support/hooks.rb:331 0.459
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.211
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.332
And I log in to a new session 9.284
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.813
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.806
Then the running Tails is installed on USB drive "to_upgrade" 15.263
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 2.305
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.156
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.670
Then all tps features from the old Tails version are active 0.904
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.367
And the expected persistent files created with the old Tails version are present in the filesystem 1.088
And all persistent directories from the old Tails version have safe access rights 1.845
After features/support/hooks.rb:331 0.553
After features/support/hooks.rb:100 0.007
4:29.961
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 8.243
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.201
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.016
And Tor is ready 19.945
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.356
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.228
Given I shutdown Tails and wait for the computer to power off 19.640
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.523
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.107
And the file system changes introduced in version 6.2~testoverlayfs are present 0.191
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.205
When the network is plugged 0.015
And Tor is ready 20.964
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.393
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.129
Given I shutdown Tails and wait for the computer to power off 17.102
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.229
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.256
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.016
And Tor is ready 21.751
Then the Upgrader considers the system as up-to-date 0.100
# 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.203
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.335
After features/support/hooks.rb:331 0.946
After features/support/hooks.rb:100 0.011
24.435
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.604
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.063
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 16.049
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.378
After features/support/hooks.rb:331 0.754
After features/support/hooks.rb:100 0.000