Project Number Date
test_Tails_ISO_devel 4617 14 Sep 2026, 18:42

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:41.590 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:7.754
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.444
When I start Tails from USB drive "old" with network unplugged 50.462
Then the boot device has safe access rights 2.152
And Tails is running from USB drive "old" 0.185
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.026
And udev-watchdog is monitoring the correct device 0.163
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.724
After features/support/hooks.rb:108 0.009
Tags: @product
1:23.729
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 49.164
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 23.942
And I take note of which tps features are available 7.026
Then a Tails persistence partition exists on USB drive "old" 0.526
And I shutdown Tails and wait for the computer to power off 2.741
After features/support/hooks.rb:339 0.126
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.587
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.457
Then Tails is running from USB drive "old" 0.223
And all tps features are active 7.411
When I write some files expected to persist 1.125
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.295
And all persistent directories from the old Tails version have safe access rights 1.718
And I take note of which tps features are available 6.517
And I shutdown Tails and wait for the computer to power off 4.065
# 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.485
After features/support/hooks.rb:339 0.235
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.938
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.363
And I log in to a new session 12.320
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.949
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.219
Then the running Tails is installed on USB drive "to_upgrade" 18.642
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.558
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.372
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.836
Then all tps features from the old Tails version are active 1.191
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.426
And the expected persistent files created with the old Tails version are present in the filesystem 1.025
And all persistent directories from the old Tails version have safe access rights 1.574
After features/support/hooks.rb:339 0.843
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:39.476
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 8.132
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.346
When the network is plugged 0.029
And Tor is ready 13.405
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.988
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.103
Given I shutdown Tails and wait for the computer to power off 5.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.124
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.591
And the file system changes introduced in version 6.2~testoverlayfs are present 0.192
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.087
# 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.035
And Tor is ready 9.591
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.946
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.557
Given I shutdown Tails and wait for the computer to power off 4.003
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.986
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.727
And the file system changes introduced in version 6.3~testoverlayfs are present 0.377
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.112
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.173
When the network is plugged 0.025
And Tor is ready 10.451
Then the Upgrader considers the system as up-to-date 10.391
# 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.500
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:339 0.821
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
31.731
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 21.201
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.029
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 8.070
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.019
After features/support/hooks.rb:339 0.910
After features/support/hooks.rb:108 0.000