Project Number Date
test_Tails_ISO_devel 4575 28 Aug 2026, 11:13

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 10:58.336 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
55.337
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.007
When I start Tails from USB drive "old" with network unplugged 38.220
Then the boot device has safe access rights 2.202
And Tails is running from USB drive "old" 0.213
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.705
After features/support/hooks.rb:108 0.014
Tags: @product
1:24.082
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 48.640
Then Tails is running from USB drive "old" 0.196
And I create a persistent partition 23.473
And I take note of which tps features are available 6.364
Then a Tails persistence partition exists on USB drive "old" 1.272
And I shutdown Tails and wait for the computer to power off 4.053
After features/support/hooks.rb:339 0.287
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.271
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.916
Then Tails is running from USB drive "old" 0.203
And all tps features are active 6.950
When I write some files expected to persist 1.188
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.231
And all persistent directories from the old Tails version have safe access rights 1.598
And I take note of which tps features are available 6.250
And I shutdown Tails and wait for the computer to power off 2.538
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.136
After features/support/hooks.rb:339 0.732
After features/support/hooks.rb:108 0.037
Tags: @product
2:11.861
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.582
And I log in to a new session 11.388
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.718
And I plug USB drive "to_upgrade" 2.282
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.648
Then the running Tails is installed on USB drive "to_upgrade" 17.985
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.690
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.895
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.608
Then all tps features from the old Tails version are active 1.045
And Tails is running from USB drive "to_upgrade" 0.191
And the boot device has safe access rights 2.062
And the expected persistent files created with the old Tails version are present in the filesystem 0.905
And all persistent directories from the old Tails version have safe access rights 1.999
After features/support/hooks.rb:339 0.767
After features/support/hooks.rb:108 0.005
3:29.881
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.305
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.023
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.320
When the network is plugged 0.024
And Tor is ready 13.065
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.541
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.453
Given I shutdown Tails and wait for the computer to power off 5.267
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.227
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 8.443
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.183
When the network is plugged 0.025
And Tor is ready 10.087
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.539
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.325
Given I shutdown Tails and wait for the computer to power off 2.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.965
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 7.316
And the file system changes introduced in version 6.3~testoverlayfs are present 0.314
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.091
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.181
When the network is plugged 0.032
And Tor is ready 10.934
Then the Upgrader considers the system as up-to-date 0.097
# 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.175
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.323
After features/support/hooks.rb:339 0.985
After features/support/hooks.rb:108 0.026
19.006
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.017
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
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.079
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.775
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.833
After features/support/hooks.rb:339 0.644
After features/support/hooks.rb:108 0.000