Project Number Date
test_Tails_ISO_devel 4155 07 Jan 2026, 08: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:12.279 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.020
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.857
When I start Tails from USB drive "old" with network unplugged 47.890
Then the boot device has safe access rights 2.446
And Tails is running from USB drive "old" 0.249
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:331 3.548
After features/support/hooks.rb:100 0.026
Tags: @product
1:26.696
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 53.038
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 23.812
And I take note of which tps features are available 0.714
Then a Tails persistence partition exists on USB drive "old" 0.541
And I shutdown Tails and wait for the computer to power off 8.279
After features/support/hooks.rb:331 0.179
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.993
Then Tails is running from USB drive "old" 0.293
And all tps features are active 1.106
When I write some files expected to persist 1.491
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 1.888
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 8.093
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.374
After features/support/hooks.rb:331 0.279
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.667
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 without a persistent partition and stopped at Tails Greeter's login screen 8.592
And I log in to a new session 13.139
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.848
And I plug USB drive "to_upgrade" 2.316
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.210
Then the running Tails is installed on USB drive "to_upgrade" 15.207
And I unplug USB drive "to_upgrade" 0.177
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:331 0.999
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.430
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.680
Then all tps features from the old Tails version are active 1.082
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 2.954
And the expected persistent files created with the old Tails version are present in the filesystem 1.225
And all persistent directories from the old Tails version have safe access rights 2.137
After features/support/hooks.rb:331 0.816
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:27.342
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.353
And no SquashFS delta is installed 0.134
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.370
When the network is plugged 0.017
And Tor is ready 12.895
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.200
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.234
Given I shutdown Tails and wait for the computer to power off 9.761
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.098
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.133
And the file system changes introduced in version 6.2~testoverlayfs are present 0.244
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.210
# 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.266
When the network is plugged 0.017
And Tor is ready 10.354
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.597
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.388
Given I shutdown Tails and wait for the computer to power off 8.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.666
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.202
And the file system changes introduced in version 6.3~testoverlayfs are present 0.364
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.019
And Tor is ready 11.021
Then the Upgrader considers the system as up-to-date 0.092
# 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 3.845
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.319
After features/support/hooks.rb:331 1.095
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
20.043
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 7.585
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.041
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 11.053
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.028
After features/support/hooks.rb:331 0.645
After features/support/hooks.rb:100 0.000