Project Number Date
test_Tails_ISO_stable 6053 12 Jan 2026, 16: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:19.261 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.821
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.720
When I start Tails from USB drive "old" with network unplugged 41.603
Then the boot device has safe access rights 2.682
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 3.812
After features/support/hooks.rb:100 0.014
Tags: @product
1:30.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 55.534
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 25.241
And I take note of which tps features are available 0.737
Then a Tails persistence partition exists on USB drive "old" 0.990
And I shutdown Tails and wait for the computer to power off 7.272
After features/support/hooks.rb:331 0.309
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.775
Then Tails is running from USB drive "old" 0.238
And all tps features are active 1.098
When I write some files expected to persist 1.234
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.149
And all persistence configuration files have safe access rights 0.266
And all persistent directories from the old Tails version have safe access rights 1.711
And I take note of which tps features are available 0.136
And I shutdown Tails and wait for the computer to power off 8.058
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.136
After features/support/hooks.rb:331 0.578
After features/support/hooks.rb:100 0.006
Tags: @product
2:10.969
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 7.832
And I log in to a new session 11.784
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.731
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.693
Then the running Tails is installed on USB drive "to_upgrade" 16.344
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:331 3.897
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.670
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.948
Then all tps features from the old Tails version are active 0.950
And Tails is running from USB drive "to_upgrade" 0.211
And the boot device has safe access rights 2.495
And the expected persistent files created with the old Tails version are present in the filesystem 1.113
And all persistent directories from the old Tails version have safe access rights 1.895
After features/support/hooks.rb:331 0.577
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:43.365
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 with a persistent partition enabled and logged in 8.981
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
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.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.016
And Tor is ready 12.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.555
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.543
Given I shutdown Tails and wait for the computer to power off 9.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.784
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.227
And the file system changes introduced in version 6.2~testoverlayfs are present 0.256
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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 1.270
When the network is plugged 0.016
And Tor is ready 11.183
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.925
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.957
Given I shutdown Tails and wait for the computer to power off 8.079
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.075
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.188
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.015
And Tor is ready 10.387
Then the Upgrader considers the system as up-to-date 10.560
# 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.786
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.358
After features/support/hooks.rb:331 1.148
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
19.418
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.613
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
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.014
And Tor is ready 9.538
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.827
After features/support/hooks.rb:331 0.826
After features/support/hooks.rb:100 0.000