Project Number Date
test_Tails_ISO_stable 6242 28 Mar 2026, 07:11

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:54.727 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:27.601
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.287
When I start Tails from USB drive "old" with network unplugged 1:8.202
Then the boot device has safe access rights 3.307
And Tails is running from USB drive "old" 0.257
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.236
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 2.004
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.218
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 55.565
Then Tails is running from USB drive "old" 0.267
And I create a persistent partition 24.603
And I take note of which tps features are available 0.812
Then a Tails persistence partition exists on USB drive "old" 0.605
And I shutdown Tails and wait for the computer to power off 8.309
After features/support/hooks.rb:331 0.274
After features/support/hooks.rb:100 0.009
Tags: @product
1:26.078
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.880
Then Tails is running from USB drive "old" 0.310
And all tps features are active 1.178
When I write some files expected to persist 1.650
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.481
And all persistent directories from the old Tails version have safe access rights 2.218
And I take note of which tps features are available 0.155
And I shutdown Tails and wait for the computer to power off 4.184
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.728
After features/support/hooks.rb:331 0.293
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.925
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 8.945
And I log in to a new session 13.474
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.557
And I plug USB drive "to_upgrade" 2.275
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.713
Then the running Tails is installed on USB drive "to_upgrade" 16.644
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:331 2.964
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.631
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.226
Then all tps features from the old Tails version are active 0.994
And Tails is running from USB drive "to_upgrade" 0.277
And the boot device has safe access rights 2.866
And the expected persistent files created with the old Tails version are present in the filesystem 1.187
And all persistent directories from the old Tails version have safe access rights 1.992
After features/support/hooks.rb:331 0.701
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:34.140
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.430
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.016
And Tor is ready 21.579
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.038
Given I shutdown Tails and wait for the computer to power off 15.164
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.370
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.246
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.161
# 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.222
When the network is plugged 0.028
And Tor is ready 22.325
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.390
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.215
Given I shutdown Tails and wait for the computer to power off 13.547
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.796
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.258
And the file system changes introduced in version 6.3~testoverlayfs are present 0.365
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.017
And Tor is ready 20.409
Then the Upgrader considers the system as up-to-date 0.107
# 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.838
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.409
After features/support/hooks.rb:331 0.832
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
27.130
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.375
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
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.016
And Tor is ready 17.939
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.463
After features/support/hooks.rb:331 0.887
After features/support/hooks.rb:100 0.000