Project Number Date
test_Tails_ISO_stable 5970 26 Nov 2025, 13:54

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 15:50.683 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
2:8.161
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.368
When I start Tails from USB drive "old" with network unplugged 1:32.386
Then the boot device has safe access rights 3.287
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.255
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:331 3.562
After features/support/hooks.rb:100 0.009
Tags: @product
2:1.435
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:24.618
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 29.492
And I take note of which tps features are available 1.200
Then a Tails persistence partition exists on USB drive "old" 0.683
And I shutdown Tails and wait for the computer to power off 4.949
After features/support/hooks.rb:331 0.566
After features/support/hooks.rb:100 0.008
Tags: @product
2:8.067
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.300
Then Tails is running from USB drive "old" 0.293
And all tps features are active 1.890
When I write some files expected to persist 1.398
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 2.004
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 7.990
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.024
After features/support/hooks.rb:331 0.349
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.855
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.031
And I log in to a new session 12.114
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.582
And I plug USB drive "to_upgrade" 2.557
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.230
Then the running Tails is installed on USB drive "to_upgrade" 19.944
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:331 4.118
After features/support/hooks.rb:100 0.000
Tags: @product
1:48.640
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:39.854
Then all tps features from the old Tails version are active 1.348
And Tails is running from USB drive "to_upgrade" 0.273
And the boot device has safe access rights 3.076
And the expected persistent files created with the old Tails version are present in the filesystem 1.361
And all persistent directories from the old Tails version have safe access rights 2.472
After features/support/hooks.rb:331 0.899
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:53.948
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 with a persistent partition enabled and logged in 12.590
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.057
And Tor is ready 13.021
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.726
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.101
Given I shutdown Tails and wait for the computer to power off 7.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.021
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.173
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# 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.215
When the network is plugged 0.051
And Tor is ready 10.743
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.964
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.346
Given I shutdown Tails and wait for the computer to power off 8.089
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.423
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.289
And the file system changes introduced in version 6.3~testoverlayfs are present 0.427
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.054
And Tor is ready 13.794
Then the Upgrader considers the system as up-to-date 0.213
# 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.129
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.519
After features/support/hooks.rb:331 1.208
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
22.574
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 10.198
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 10.066
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.861
After features/support/hooks.rb:331 0.761
After features/support/hooks.rb:100 0.000