Project Number Date
test_Tails_ISO_devel 4219 09 Feb 2026, 11:47

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 11:17.471 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
59.108
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.487
When I start Tails from USB drive "old" with network unplugged 41.234
Then the boot device has safe access rights 2.598
And Tails is running from USB drive "old" 0.267
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 3.462
After features/support/hooks.rb:100 0.024
Tags: @product
1:28.215
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 52.939
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 25.119
And I take note of which tps features are available 0.881
Then a Tails persistence partition exists on USB drive "old" 0.710
And I shutdown Tails and wait for the computer to power off 8.229
After features/support/hooks.rb:331 0.635
After features/support/hooks.rb:100 0.008
Tags: @product
1:27.001
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.499
Then Tails is running from USB drive "old" 0.273
And all tps features are active 1.040
When I write some files expected to persist 1.209
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.275
And all persistent directories from the old Tails version have safe access rights 1.855
And I take note of which tps features are available 0.132
And I shutdown Tails and wait for the computer to power off 8.034
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.425
After features/support/hooks.rb:331 0.302
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.176
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.163
And I log in to a new session 9.576
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.823
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.501
Then the running Tails is installed on USB drive "to_upgrade" 16.568
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:331 0.644
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.911
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.254
Then all tps features from the old Tails version are active 0.958
And Tails is running from USB drive "to_upgrade" 0.262
And the boot device has safe access rights 2.778
And the expected persistent files created with the old Tails version are present in the filesystem 1.183
And all persistent directories from the old Tails version have safe access rights 2.407
After features/support/hooks.rb:331 0.842
After features/support/hooks.rb:100 0.039
3:40.924
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.484
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.016
And Tor is ready 13.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.952
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.934
Given I shutdown Tails and wait for the computer to power off 11.247
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.527
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.282
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.240
When the network is plugged 0.014
And Tor is ready 10.399
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.037
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.705
Given I shutdown Tails and wait for the computer to power off 8.058
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.962
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.112
And the file system changes introduced in version 6.3~testoverlayfs are present 0.589
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.199
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.017
And Tor is ready 16.987
Then the Upgrader considers the system as up-to-date 0.095
# 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.035
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.493
After features/support/hooks.rb:331 1.055
After features/support/hooks.rb:100 0.013
19.133
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 7.607
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 9.976
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.206
After features/support/hooks.rb:331 0.682
After features/support/hooks.rb:100 0.000