Project Number Date
test_Tails_ISO_devel 4373 04 May 2026, 10:59

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:35.139 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.248
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.823
When I start Tails from USB drive "old" with network unplugged 47.932
Then the boot device has safe access rights 2.640
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:331 1.291
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.934
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 55.019
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 25.463
And I take note of which tps features are available 0.951
Then a Tails persistence partition exists on USB drive "old" 0.620
And I shutdown Tails and wait for the computer to power off 8.587
After features/support/hooks.rb:331 0.481
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.905
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.412
Then Tails is running from USB drive "old" 0.270
And all tps features are active 1.143
When I write some files expected to persist 1.316
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.495
And all persistent directories from the old Tails version have safe access rights 1.963
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 8.627
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.274
After features/support/hooks.rb:331 0.500
After features/support/hooks.rb:100 0.006
Tags: @product
2:11.686
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 7.694
And I log in to a new session 12.143
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.109
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.707
Then the running Tails is installed on USB drive "to_upgrade" 16.525
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:331 0.775
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.646
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.098
Then all tps features from the old Tails version are active 1.157
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.614
And the expected persistent files created with the old Tails version are present in the filesystem 1.307
And all persistent directories from the old Tails version have safe access rights 2.176
After features/support/hooks.rb:331 0.657
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:37.993
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.448
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.016
And Tor is ready 21.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.378
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.976
Given I shutdown Tails and wait for the computer to power off 14.869
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.306
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.200
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.186
# 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.228
When the network is plugged 0.017
And Tor is ready 21.920
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.379
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.575
Given I shutdown Tails and wait for the computer to power off 17.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.830
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.136
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.017
And Tor is ready 21.078
Then the Upgrader considers the system as up-to-date 0.127
# 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.987
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.418
After features/support/hooks.rb:331 0.954
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
26.723
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 7.607
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.048
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 18.379
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.377
After features/support/hooks.rb:331 1.027
After features/support/hooks.rb:100 0.000