Project Number Date
test_Tails_ISO_devel 4664 08 Oct 2026, 07:40

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 12:3.228 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:17.148
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 13.979
When I start Tails from USB drive "old" with network unplugged 59.111
Then the boot device has safe access rights 2.314
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.031
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.158
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.492
After features/support/hooks.rb:108 0.032
Tags: @product
1:29.132
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login 50.834
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 24.006
And I take note of which tps features are available 7.652
Then a Tails persistence partition exists on USB drive "old" 0.579
And I shutdown Tails and wait for the computer to power off 5.704
After features/support/hooks.rb:339 0.288
After features/support/hooks.rb:108 0.025
Tags: @product
1:42.086
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.133
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.357
Then Tails is running from USB drive "old" 0.237
And all tps features are active 8.277
When I write some files expected to persist 1.628
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.161
And all persistence configuration files have safe access rights 0.337
And all persistent directories from the old Tails version have safe access rights 2.817
And I take note of which tps features are available 7.014
And I shutdown Tails and wait for the computer to power off 2.863
# 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" 12.258
After features/support/hooks.rb:339 0.261
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.497
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.826
And I log in to a new session 12.663
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.765
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.231
Then the running Tails is installed on USB drive "to_upgrade" 19.503
And I unplug USB drive "to_upgrade" 0.110
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 3.672
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.924
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.297
Then all tps features from the old Tails version are active 1.388
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.629
And the expected persistent files created with the old Tails version are present in the filesystem 1.097
And all persistent directories from the old Tails version have safe access rights 2.185
After features/support/hooks.rb:339 0.787
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:43.407
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.706
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.040
And Tor is ready 13.571
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.305
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.613
Given I shutdown Tails and wait for the computer to power off 5.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.291
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.880
And the file system changes introduced in version 6.2~testoverlayfs are present 0.238
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.107
# 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.247
When the network is plugged 0.044
And Tor is ready 10.428
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.978
Given I shutdown Tails and wait for the computer to power off 4.175
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.021
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 11.317
And the file system changes introduced in version 6.3~testoverlayfs are present 0.363
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.112
And Tor is ready 10.736
Then the Upgrader considers the system as up-to-date 0.094
# 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.667
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.951
After features/support/hooks.rb:108 0.049
Tags: @product @automatic_upgrade
20.031
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.204
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 9.854
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.563
After features/support/hooks.rb:339 0.681
After features/support/hooks.rb:108 0.000