Project Number Date
test_Tails_ISO_stable 6106 30 Jan 2026, 08:18

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:39.272 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:44.271
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.366
When I start Tails from USB drive "old" with network unplugged 1:7.840
Then the boot device has safe access rights 2.981
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:331 4.027
After features/support/hooks.rb:100 0.029
Tags: @product
1:39.417
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login 1:1.562
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 28.117
And I take note of which tps features are available 1.165
Then a Tails persistence partition exists on USB drive "old" 0.688
And I shutdown Tails and wait for the computer to power off 7.407
After features/support/hooks.rb:331 0.569
After features/support/hooks.rb:100 0.009
Tags: @product
1:42.485
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.858
Then Tails is running from USB drive "old" 0.305
And all tps features are active 1.697
When I write some files expected to persist 1.392
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 2.230
And I take note of which tps features are available 0.403
And I shutdown Tails and wait for the computer to power off 7.366
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.521
After features/support/hooks.rb:331 0.453
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.974
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 10.839
And I log in to a new session 12.886
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.320
And I plug USB drive "to_upgrade" 2.345
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.249
Then the running Tails is installed on USB drive "to_upgrade" 19.940
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:331 3.795
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.520
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.160
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.296
Then all tps features from the old Tails version are active 1.324
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.949
And the expected persistent files created with the old Tails version are present in the filesystem 1.285
And all persistent directories from the old Tails version have safe access rights 2.243
After features/support/hooks.rb:331 0.829
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:25.135
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.644
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
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.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.093
And Tor is ready 43.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.586
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.532
Given I shutdown Tails and wait for the computer to power off 7.666
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.113
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.934
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.228
When the network is plugged 0.057
And Tor is ready 11.597
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.666
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.621
Given I shutdown Tails and wait for the computer to power off 7.381
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.213
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.868
And the file system changes introduced in version 6.3~testoverlayfs are present 0.429
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.052
And Tor is ready 10.776
Then the Upgrader considers the system as up-to-date 0.111
# 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.014
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.455
After features/support/hooks.rb:331 0.957
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
21.467
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 9.434
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 11.068
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.558
After features/support/hooks.rb:331 0.876
After features/support/hooks.rb:100 0.000