Project Number Date
test_Tails_ISO_stable 6183 04 Mar 2026, 08:24

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 16:16.271 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:48.664
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 32.027
When I start Tails from USB drive "old" with network unplugged 1:11.258
Then the boot device has safe access rights 3.270
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:331 1.683
After features/support/hooks.rb:100 0.008
Tags: @product
1:43.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 1:4.518
Then Tails is running from USB drive "old" 0.764
And I create a persistent partition 28.626
And I take note of which tps features are available 1.178
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 7.717
After features/support/hooks.rb:331 0.277
After features/support/hooks.rb:100 0.009
Tags: @product
1:50.803
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:17.193
Then Tails is running from USB drive "old" 0.338
And all tps features are active 1.952
When I write some files expected to persist 1.696
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.508
And all persistent directories from the old Tails version have safe access rights 2.233
And I take note of which tps features are available 0.398
And I shutdown Tails and wait for the computer to power off 7.651
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.460
After features/support/hooks.rb:331 0.606
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.266
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 23.164
And I log in to a new session 14.153
And I clone USB drive "old" to a new USB drive "to_upgrade" 8.040
And I plug USB drive "to_upgrade" 2.536
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.382
Then the running Tails is installed on USB drive "to_upgrade" 21.559
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:331 3.072
After features/support/hooks.rb:100 0.000
Tags: @product
1:26.554
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:17.905
Then all tps features from the old Tails version are active 1.385
And Tails is running from USB drive "to_upgrade" 0.277
And the boot device has safe access rights 3.022
And the expected persistent files created with the old Tails version are present in the filesystem 1.334
And all persistent directories from the old Tails version have safe access rights 2.467
After features/support/hooks.rb:331 0.972
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
5:55.721
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 13.128
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
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.367
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.064
And Tor is ready 26.261
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.628
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.439
Given I shutdown Tails and wait for the computer to power off 21.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:30.645
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.561
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.172
# 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.285
When the network is plugged 0.058
And Tor is ready 40.860
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.575
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.961
Given I shutdown Tails and wait for the computer to power off 18.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:30.431
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.496
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.225
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.056
And Tor is ready 24.081
Then the Upgrader considers the system as up-to-date 0.130
# 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.875
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.598
After features/support/hooks.rb:331 1.119
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
34.533
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 12.551
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
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.072
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 20.959
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.577
After features/support/hooks.rb:331 1.266
After features/support/hooks.rb:100 0.000