Project Number Date
test_Tails_ISO_stable 6210 17 Mar 2026, 07:14

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:12.743 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:42.598
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.480
When I start Tails from USB drive "old" with network unplugged 1:24.711
Then the boot device has safe access rights 2.660
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 3.434
After features/support/hooks.rb:100 0.021
Tags: @product
1:25.845
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 52.953
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 23.505
And I take note of which tps features are available 0.713
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 7.824
After features/support/hooks.rb:331 0.560
After features/support/hooks.rb:100 0.011
Tags: @product
1:25.455
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.984
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.130
When I write some files expected to persist 1.235
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 1.842
And I take note of which tps features are available 0.154
And I shutdown Tails and wait for the computer to power off 7.874
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.289
After features/support/hooks.rb:331 0.392
After features/support/hooks.rb:100 0.006
Tags: @product
2:16.893
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.972
And I log in to a new session 14.268
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.650
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.803
Then the running Tails is installed on USB drive "to_upgrade" 15.644
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:331 3.842
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.425
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.473
Then all tps features from the old Tails version are active 1.051
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 2.459
And the expected persistent files created with the old Tails version are present in the filesystem 1.120
And all persistent directories from the old Tails version have safe access rights 1.970
After features/support/hooks.rb:331 2.882
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:37.557
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.248
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.329
When the network is plugged 0.014
And Tor is ready 23.430
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.452
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.568
Given I shutdown Tails and wait for the computer to power off 23.467
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.132
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.116
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.015
And Tor is ready 20.933
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.343
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.699
Given I shutdown Tails and wait for the computer to power off 13.182
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.974
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.069
And the file system changes introduced in version 6.3~testoverlayfs are present 0.412
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.014
And Tor is ready 21.610
Then the Upgrader considers the system as up-to-date 0.099
# 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.328
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.317
After features/support/hooks.rb:331 0.719
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
27.968
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.572
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 19.658
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.426
After features/support/hooks.rb:331 0.803
After features/support/hooks.rb:100 0.000