Project Number Date
test_Tails_ISO_devel 4223 10 Feb 2026, 08:40

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:32.362 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
58.313
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.437
When I start Tails from USB drive "old" with network unplugged 40.683
Then the boot device has safe access rights 2.428
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.165
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 1.294
After features/support/hooks.rb:100 0.005
Tags: @product
1:24.855
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 51.117
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 24.252
And I take note of which tps features are available 0.627
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.896
After features/support/hooks.rb:331 0.465
After features/support/hooks.rb:100 0.007
Tags: @product
1:19.851
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.762
Then Tails is running from USB drive "old" 0.227
And all tps features are active 1.073
When I write some files expected to persist 1.231
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.274
And all persistent directories from the old Tails version have safe access rights 1.747
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 3.913
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.253
After features/support/hooks.rb:331 0.527
After features/support/hooks.rb:100 0.006
Tags: @product
2:21.276
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.757
And I log in to a new session 12.727
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.742
And I plug USB drive "to_upgrade" 2.261
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.200
Then the running Tails is installed on USB drive "to_upgrade" 16.265
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:331 3.735
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.596
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.823
Then all tps features from the old Tails version are active 0.840
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.619
And the expected persistent files created with the old Tails version are present in the filesystem 1.159
And all persistent directories from the old Tails version have safe access rights 1.866
After features/support/hooks.rb:331 0.613
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:57.547
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.515
And no SquashFS delta is installed 0.152
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.305
When the network is plugged 0.019
And Tor is ready 12.691
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.626
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.969
Given I shutdown Tails and wait for the computer to power off 13.857
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.161
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.108
And the file system changes introduced in version 6.2~testoverlayfs are present 0.196
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.205
When the network is plugged 0.015
And Tor is ready 11.130
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.392
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.757
Given I shutdown Tails and wait for the computer to power off 7.866
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.777
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.095
And the file system changes introduced in version 6.3~testoverlayfs are present 0.368
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.017
And Tor is ready 10.230
Then the Upgrader considers the system as up-to-date 10.542
# 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 4.096
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.325
After features/support/hooks.rb:331 1.027
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
20.920
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.590
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 11.218
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.786
After features/support/hooks.rb:331 0.863
After features/support/hooks.rb:100 0.000