Project Number Date
test_Tails_ISO_devel 4278 13 Mar 2026, 11:21

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:59.991 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:5.553
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.958
When I start Tails from USB drive "old" with network unplugged 46.771
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 1.372
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.231
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 54.168
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 25.044
And I take note of which tps features are available 0.747
Then a Tails persistence partition exists on USB drive "old" 0.601
And I shutdown Tails and wait for the computer to power off 8.357
After features/support/hooks.rb:331 0.231
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.599
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.152
Then Tails is running from USB drive "old" 0.286
And all tps features are active 1.380
When I write some files expected to persist 1.317
# 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.447
And all persistent directories from the old Tails version have safe access rights 1.993
And I take note of which tps features are available 0.202
And I shutdown Tails and wait for the computer to power off 7.975
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.626
After features/support/hooks.rb:331 0.240
After features/support/hooks.rb:100 0.006
Tags: @product
2:17.697
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.665
And I log in to a new session 13.493
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.878
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.455
Then the running Tails is installed on USB drive "to_upgrade" 17.714
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:331 3.105
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.061
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.277
Then all tps features from the old Tails version are active 1.324
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.695
And the expected persistent files created with the old Tails version are present in the filesystem 1.383
And all persistent directories from the old Tails version have safe access rights 2.057
After features/support/hooks.rb:331 0.783
After features/support/hooks.rb:100 0.040
Tags: @product @automatic_upgrade
4:55.626
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.424
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.200
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.347
When the network is plugged 0.016
And Tor is ready 29.159
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.412
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.659
Given I shutdown Tails and wait for the computer to power off 19.860
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.679
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.269
And the file system changes introduced in version 6.2~testoverlayfs are present 0.256
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.218
When the network is plugged 0.017
And Tor is ready 22.600
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.361
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.311
Given I shutdown Tails and wait for the computer to power off 17.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.465
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.064
And the file system changes introduced in version 6.3~testoverlayfs are present 0.347
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.016
And Tor is ready 21.995
Then the Upgrader considers the system as up-to-date 0.109
# 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.804
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.367
After features/support/hooks.rb:331 1.162
After features/support/hooks.rb:100 0.079
Tags: @product @automatic_upgrade
28.221
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.005
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.099
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 19.322
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.445
After features/support/hooks.rb:331 1.030
After features/support/hooks.rb:100 0.000