Project Number Date
test_Tails_ISO_stable 6060 14 Jan 2026, 12:56

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 14:56.600 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:51.527
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.070
And I plug USB drive "old" 1.091
And I write an old version of the Tails USB image to disk "old" 31.231
When I start Tails from USB drive "old" with network unplugged 1:14.746
Then the boot device has safe access rights 3.281
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.256
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:331 4.009
After features/support/hooks.rb:100 0.010
Tags: @product
1:40.610
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:6.153
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 28.867
And I take note of which tps features are available 1.127
Then a Tails persistence partition exists on USB drive "old" 0.691
And I shutdown Tails and wait for the computer to power off 3.223
After features/support/hooks.rb:331 0.359
After features/support/hooks.rb:100 0.010
Tags: @product
1:52.544
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:18.654
Then Tails is running from USB drive "old" 0.338
And all tps features are active 2.013
When I write some files expected to persist 1.991
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 2.373
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 7.910
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.954
After features/support/hooks.rb:331 0.406
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.229
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 without a persistent partition and stopped at Tails Greeter's login screen 12.737
And I log in to a new session 13.737
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.593
And I plug USB drive "to_upgrade" 2.835
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.881
Then the running Tails is installed on USB drive "to_upgrade" 21.042
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:331 3.883
After features/support/hooks.rb:100 0.000
Tags: @product
1:27.526
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.278
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:18.778
Then all tps features from the old Tails version are active 1.382
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.086
And the expected persistent files created with the old Tails version are present in the filesystem 1.403
And all persistent directories from the old Tails version have safe access rights 2.255
After features/support/hooks.rb:331 1.098
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
4:48.951
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 12.659
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
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.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.067
And Tor is ready 13.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.973
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.661
Given I shutdown Tails and wait for the computer to power off 11.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.657
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.196
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.226
# 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.270
When the network is plugged 0.063
And Tor is ready 41.962
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.619
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.957
Given I shutdown Tails and wait for the computer to power off 7.984
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.104
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.540
And the file system changes introduced in version 6.3~testoverlayfs are present 0.421
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.193
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.223
When the network is plugged 0.060
And Tor is ready 10.760
Then the Upgrader considers the system as up-to-date 0.135
# 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 5.912
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.542
After features/support/hooks.rb:331 1.211
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
25.211
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 11.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
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.060
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 11.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.763
After features/support/hooks.rb:331 2.113
After features/support/hooks.rb:100 0.000