Project Number Date
test_Tails_ISO_stable 6097 27 Jan 2026, 19:17

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 11:40.373 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:12.904
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.781
When I start Tails from USB drive "old" with network unplugged 54.437
Then the boot device has safe access rights 2.934
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 3.887
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.341
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 56.213
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 24.942
And I take note of which tps features are available 0.793
Then a Tails persistence partition exists on USB drive "old" 0.528
And I shutdown Tails and wait for the computer to power off 8.557
After features/support/hooks.rb:331 0.537
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.822
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.450
Then Tails is running from USB drive "old" 0.265
And all tps features are active 1.093
When I write some files expected to persist 1.333
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.327
And all persistent directories from the old Tails version have safe access rights 2.108
And I take note of which tps features are available 0.166
And I shutdown Tails and wait for the computer to power off 8.377
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.489
After features/support/hooks.rb:331 0.565
After features/support/hooks.rb:100 0.007
Tags: @product
2:14.035
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 without a persistent partition and stopped at Tails Greeter's login screen 9.168
And I log in to a new session 10.535
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.925
And I plug USB drive "to_upgrade" 2.256
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.589
Then the running Tails is installed on USB drive "to_upgrade" 17.289
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:331 2.584
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.255
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.113
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.628
Then all tps features from the old Tails version are active 1.055
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 2.777
And the expected persistent files created with the old Tails version are present in the filesystem 1.201
And all persistent directories from the old Tails version have safe access rights 2.116
After features/support/hooks.rb:331 0.624
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
3:41.334
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 8.400
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.015
And Tor is ready 14.216
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.364
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.588
Given I shutdown Tails and wait for the computer to power off 10.933
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.233
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.238
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.319
When the network is plugged 0.166
And Tor is ready 11.640
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.155
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.315
Given I shutdown Tails and wait for the computer to power off 8.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.101
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.105
And the file system changes introduced in version 6.3~testoverlayfs are present 0.338
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.200
When the network is plugged 0.019
And Tor is ready 11.821
Then the Upgrader considers the system as up-to-date 0.143
# 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.307
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:331 1.152
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
19.680
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.475
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 11.489
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.385
After features/support/hooks.rb:331 1.120
After features/support/hooks.rb:100 0.000