Project Number Date
test_Tails_ISO_devel 4552 17 Aug 2026, 11:17

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:13.785 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:2.430
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
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.294
When I start Tails from USB drive "old" with network unplugged 45.545
Then the boot device has safe access rights 1.931
And Tails is running from USB drive "old" 0.166
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.102
After features/support/hooks.rb:339 3.628
After features/support/hooks.rb:108 0.047
Tags: @product
1:19.638
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 46.876
Then Tails is running from USB drive "old" 0.188
And I create a persistent partition 23.135
And I take note of which tps features are available 6.209
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 2.625
After features/support/hooks.rb:339 0.188
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.879
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.121
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.163
Then Tails is running from USB drive "old" 0.239
And all tps features are active 7.747
When I write some files expected to persist 1.228
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.293
And all persistent directories from the old Tails version have safe access rights 1.831
And I take note of which tps features are available 6.949
And I shutdown Tails and wait for the computer to power off 2.700
# 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.419
After features/support/hooks.rb:339 0.411
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.285
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.402
And I log in to a new session 12.804
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.750
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.263
Then the running Tails is installed on USB drive "to_upgrade" 18.557
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:339 1.556
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.615
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.129
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.775
Then all tps features from the old Tails version are active 1.221
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.423
And the expected persistent files created with the old Tails version are present in the filesystem 0.994
And all persistent directories from the old Tails version have safe access rights 1.856
After features/support/hooks.rb:339 0.601
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
3:35.363
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.335
And no SquashFS delta is installed 0.078
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.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.024
And Tor is ready 13.277
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.861
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.401
Given I shutdown Tails and wait for the computer to power off 5.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.951
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 7.858
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.201
When the network is plugged 0.038
And Tor is ready 11.108
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.331
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.783
Given I shutdown Tails and wait for the computer to power off 3.948
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.355
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.685
And the file system changes introduced in version 6.3~testoverlayfs are present 0.404
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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.026
And Tor is ready 10.321
Then the Upgrader considers the system as up-to-date 0.101
# 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.742
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.399
After features/support/hooks.rb:339 0.958
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.572
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.860
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.953
After features/support/hooks.rb:339 0.598
After features/support/hooks.rb:108 0.000