Project Number Date
test_Tails_ISO_devel 4361 23 Apr 2026, 12: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 12:57.163 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:4.348
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.026
When I start Tails from USB drive "old" with network unplugged 45.451
Then the boot device has safe access rights 2.972
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.239
And I unplug USB drive "old" 0.238
After features/support/hooks.rb:331 3.814
After features/support/hooks.rb:100 0.008
Tags: @product
1:23.497
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 54.098
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 23.364
And I take note of which tps features are available 0.753
Then a Tails persistence partition exists on USB drive "old" 0.556
And I shutdown Tails and wait for the computer to power off 4.336
After features/support/hooks.rb:331 0.372
After features/support/hooks.rb:100 0.008
Tags: @product
1:26.788
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.154
Then Tails is running from USB drive "old" 0.278
And all tps features are active 1.361
When I write some files expected to persist 1.586
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.455
And all persistent directories from the old Tails version have safe access rights 2.051
And I take note of which tps features are available 0.194
And I shutdown Tails and wait for the computer to power off 4.036
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.414
After features/support/hooks.rb:331 0.512
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.641
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 7.985
And I log in to a new session 16.530
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.758
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.691
Then the running Tails is installed on USB drive "to_upgrade" 16.153
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 3.666
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.276
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.567
Then all tps features from the old Tails version are active 0.980
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 2.414
And the expected persistent files created with the old Tails version are present in the filesystem 1.194
And all persistent directories from the old Tails version have safe access rights 1.844
After features/support/hooks.rb:331 0.988
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:41.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.495
And no SquashFS delta is installed 0.172
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.019
And Tor is ready 21.645
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.431
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.528
Given I shutdown Tails and wait for the computer to power off 20.665
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.255
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.117
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.014
And Tor is ready 20.295
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.358
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.974
Given I shutdown Tails and wait for the computer to power off 17.252
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.031
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.300
And the file system changes introduced in version 6.3~testoverlayfs are present 0.311
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.237
When the network is plugged 0.018
And Tor is ready 21.595
Then the Upgrader considers the system as up-to-date 0.107
# 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 4.376
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.363
After features/support/hooks.rb:331 1.002
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
51.188
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.312
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
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.019
And Tor is ready 42.035
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.448
After features/support/hooks.rb:331 0.594
After features/support/hooks.rb:100 0.000