Project Number Date
test_Tails_ISO_devel 4234 16 Feb 2026, 13:48

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:11.979 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:13.191
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 15.048
When I start Tails from USB drive "old" with network unplugged 51.884
Then the boot device has safe access rights 4.202
And Tails is running from USB drive "old" 0.400
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:331 1.409
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 56.358
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 25.471
And I take note of which tps features are available 0.874
Then a Tails persistence partition exists on USB drive "old" 0.647
And I shutdown Tails and wait for the computer to power off 8.358
After features/support/hooks.rb:331 0.198
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.452
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.657
Then Tails is running from USB drive "old" 0.352
And all tps features are active 1.482
When I write some files expected to persist 1.585
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.133
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 8.174
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.207
After features/support/hooks.rb:331 0.452
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.452
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 8.717
And I log in to a new session 11.537
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.814
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.941
Then the running Tails is installed on USB drive "to_upgrade" 17.842
And I unplug USB drive "to_upgrade" 0.167
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:331 2.257
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.210
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.727
Then all tps features from the old Tails version are active 1.023
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.357
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.277
After features/support/hooks.rb:331 0.525
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:59.478
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.405
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.025
And Tor is ready 13.481
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.350
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.379
Given I shutdown Tails and wait for the computer to power off 10.048
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.057
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.160
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.109
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.358
When the network is plugged 0.045
And Tor is ready 11.921
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.581
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.080
Given I shutdown Tails and wait for the computer to power off 7.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.186
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.323
And the file system changes introduced in version 6.3~testoverlayfs are present 0.426
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.015
And Tor is ready 12.072
Then the Upgrader considers the system as up-to-date 10.579
# 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 5.108
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.472
After features/support/hooks.rb:331 1.063
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
21.979
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.543
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.963
After features/support/hooks.rb:331 0.786
After features/support/hooks.rb:100 0.000