Project Number Date
test_Tails_ISO_devel 4565 22 Aug 2026, 11:10

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:43.812 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
54.892
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.988
When I start Tails from USB drive "old" with network unplugged 38.335
Then the boot device has safe access rights 1.832
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.025
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 1.721
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.204
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 46.255
Then Tails is running from USB drive "old" 0.163
And I create a persistent partition 22.551
And I take note of which tps features are available 6.042
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 2.562
After features/support/hooks.rb:339 0.214
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.925
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.240
Then Tails is running from USB drive "old" 0.199
And all tps features are active 6.801
When I write some files expected to persist 0.878
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.125
And all persistence configuration files have safe access rights 0.223
And all persistent directories from the old Tails version have safe access rights 1.275
And I take note of which tps features are available 5.631
And I shutdown Tails and wait for the computer to power off 2.591
# 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" 10.881
After features/support/hooks.rb:339 0.341
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.141
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 without a persistent partition and stopped at Tails Greeter's login screen 7.997
And I log in to a new session 9.961
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.561
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.937
Then the running Tails is installed on USB drive "to_upgrade" 17.239
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.106
After features/support/hooks.rb:339 1.691
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.094
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.452
Then all tps features from the old Tails version are active 0.983
And Tails is running from USB drive "to_upgrade" 0.159
And the boot device has safe access rights 1.982
And the expected persistent files created with the old Tails version are present in the filesystem 0.885
And all persistent directories from the old Tails version have safe access rights 1.558
After features/support/hooks.rb:339 0.517
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
3:31.178
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 7.835
And no SquashFS delta is installed 0.043
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.175
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.274
When the network is plugged 0.025
And Tor is ready 11.395
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.020
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.510
Given I shutdown Tails and wait for the computer to power off 5.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.021
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 7.291
And the file system changes introduced in version 6.2~testoverlayfs are present 0.156
And only the 6.2~testoverlayfs SquashFS delta is installed 0.024
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.094
# 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.169
When the network is plugged 0.038
And Tor is ready 10.016
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.431
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.533
Given I shutdown Tails and wait for the computer to power off 3.900
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.172
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.158
And the file system changes introduced in version 6.3~testoverlayfs are present 0.236
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.095
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.124
When the network is plugged 0.026
And Tor is ready 10.213
Then the Upgrader considers the system as up-to-date 10.427
# 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 2.952
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.266
After features/support/hooks.rb:339 0.731
After features/support/hooks.rb:108 0.027
Tags: @product @automatic_upgrade
18.376
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 7.667
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 7.909
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.483
After features/support/hooks.rb:339 0.756
After features/support/hooks.rb:108 0.000