Project Number Date
test_Tails_ISO_stable 6246 30 Mar 2026, 07:31

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 13:11.478 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:40.926
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.258
When I start Tails from USB drive "old" with network unplugged 1:21.846
Then the boot device has safe access rights 3.018
And Tails is running from USB drive "old" 0.260
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 2.097
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.692
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 57.273
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 24.403
And I take note of which tps features are available 0.784
Then a Tails persistence partition exists on USB drive "old" 0.600
And I shutdown Tails and wait for the computer to power off 8.253
After features/support/hooks.rb:331 0.220
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.976
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.725
Then Tails is running from USB drive "old" 0.268
And all tps features are active 1.068
When I write some files expected to persist 1.315
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 2.040
And I take note of which tps features are available 0.152
And I shutdown Tails and wait for the computer to power off 6.805
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.963
After features/support/hooks.rb:331 0.395
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.662
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.477
And I log in to a new session 19.725
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.968
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.717
Then the running Tails is installed on USB drive "to_upgrade" 17.021
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.370
After features/support/hooks.rb:331 6.075
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.284
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.094
Then all tps features from the old Tails version are active 0.999
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.583
And the expected persistent files created with the old Tails version are present in the filesystem 1.148
And all persistent directories from the old Tails version have safe access rights 2.142
After features/support/hooks.rb:331 1.107
After features/support/hooks.rb:100 0.009
4:28.633
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.471
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.319
When the network is plugged 0.018
And Tor is ready 22.772
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.378
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.522
Given I shutdown Tails and wait for the computer to power off 8.651
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.556
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.147
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.223
When the network is plugged 0.018
And Tor is ready 20.401
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.399
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.960
Given I shutdown Tails and wait for the computer to power off 13.672
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.224
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.247
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.169
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.017
And Tor is ready 21.049
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.960
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.439
After features/support/hooks.rb:331 0.881
After features/support/hooks.rb:100 0.019
29.302
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 with a persistent partition enabled and logged in 7.505
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.049
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 20.893
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.507
After features/support/hooks.rb:331 1.029
After features/support/hooks.rb:100 0.000