Project Number Date
test_Tails_ISO_release-process-7.7.3 3 11 May 2026, 18:08

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:24.930 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:23.458
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.762
When I start Tails from USB drive "old" with network unplugged 1:4.675
Then the boot device has safe access rights 3.126
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:331 3.675
After features/support/hooks.rb:100 0.009
Tags: @product
1:33.441
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login 58.014
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 25.300
And I take note of which tps features are available 0.695
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 8.441
After features/support/hooks.rb:331 0.453
After features/support/hooks.rb:100 0.009
Tags: @product
1:31.200
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.684
Then Tails is running from USB drive "old" 0.276
And all tps features are active 1.235
When I write some files expected to persist 1.407
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 1.863
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 8.172
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.749
After features/support/hooks.rb:331 0.165
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.488
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.613
And I log in to a new session 14.333
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.811
And I plug USB drive "to_upgrade" 2.285
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.384
Then the running Tails is installed on USB drive "to_upgrade" 17.779
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 2.266
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.614
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.026
Then all tps features from the old Tails version are active 1.108
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.672
And the expected persistent files created with the old Tails version are present in the filesystem 1.209
And all persistent directories from the old Tails version have safe access rights 2.294
After features/support/hooks.rb:331 0.733
After features/support/hooks.rb:100 0.042
4:55.334
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 with a persistent partition enabled and logged in 8.569
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.018
And Tor is ready 23.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.489
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.329
Given I shutdown Tails and wait for the computer to power off 20.462
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.997
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.223
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# 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.014
And Tor is ready 21.428
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.379
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.868
Given I shutdown Tails and wait for the computer to power off 17.741
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.851
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.303
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.019
And Tor is ready 21.474
Then the Upgrader considers the system as up-to-date 0.180
# 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.984
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.401
After features/support/hooks.rb:331 0.718
After features/support/hooks.rb:100 0.016
28.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 19.461
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.449
After features/support/hooks.rb:331 1.121
After features/support/hooks.rb:100 0.000