Project Number Date
test_Tails_ISO_stable 6084 22 Jan 2026, 12:30

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:36.417 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:40.598
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 31.141
When I start Tails from USB drive "old" with network unplugged 1:3.958
Then the boot device has safe access rights 3.395
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.249
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:331 3.854
After features/support/hooks.rb:100 0.009
Tags: @product
1:43.103
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 1:4.127
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 29.029
And I take note of which tps features are available 1.157
Then a Tails persistence partition exists on USB drive "old" 0.660
And I shutdown Tails and wait for the computer to power off 7.666
After features/support/hooks.rb:331 0.407
After features/support/hooks.rb:100 0.009
Tags: @product
1:46.900
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:14.383
Then Tails is running from USB drive "old" 0.307
And all tps features are active 1.941
When I write some files expected to persist 1.456
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.337
And all persistent directories from the old Tails version have safe access rights 2.162
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 7.880
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.642
After features/support/hooks.rb:331 0.529
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.930
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 without a persistent partition and stopped at Tails Greeter's login screen 12.640
And I log in to a new session 13.539
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.311
And I plug USB drive "to_upgrade" 2.636
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.134
Then the running Tails is installed on USB drive "to_upgrade" 21.283
And I unplug USB drive "to_upgrade" 0.178
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:331 4.064
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.266
Then all tps features from the old Tails version are active 1.341
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 3.032
And the expected persistent files created with the old Tails version are present in the filesystem 1.281
And all persistent directories from the old Tails version have safe access rights 2.407
After features/support/hooks.rb:331 0.591
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:37.359
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 12.685
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.049
And Tor is ready 14.921
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.600
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.327
Given I shutdown Tails and wait for the computer to power off 10.042
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.079
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.298
And the file system changes introduced in version 6.2~testoverlayfs are present 0.267
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.289
When the network is plugged 0.061
And Tor is ready 11.496
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.883
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.700
Given I shutdown Tails and wait for the computer to power off 4.920
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.576
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.297
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.161
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.051
And Tor is ready 40.814
Then the Upgrader considers the system as up-to-date 0.154
# 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.119
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.411
After features/support/hooks.rb:331 0.846
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
51.734
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 11.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 39.721
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.568
After features/support/hooks.rb:331 0.695
After features/support/hooks.rb:100 0.000