Project Number Date
test_Tails_ISO_stable 6039 06 Jan 2026, 08:05

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 12:38.939 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:19.880
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 15.585
When I start Tails from USB drive "old" with network unplugged 58.988
Then the boot device has safe access rights 3.330
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 4.056
After features/support/hooks.rb:100 0.009
Tags: @product
1:35.606
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login 59.532
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 25.629
And I take note of which tps features are available 0.885
Then a Tails persistence partition exists on USB drive "old" 0.622
And I shutdown Tails and wait for the computer to power off 8.496
After features/support/hooks.rb:331 0.307
After features/support/hooks.rb:100 0.009
Tags: @product
1:37.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.637
Then Tails is running from USB drive "old" 0.379
And all tps features are active 1.588
When I write some files expected to persist 1.826
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.328
And all persistent directories from the old Tails version have safe access rights 2.186
And I take note of which tps features are available 0.192
And I shutdown Tails and wait for the computer to power off 8.862
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.692
After features/support/hooks.rb:331 0.394
After features/support/hooks.rb:100 0.007
Tags: @product
2:20.282
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 9.952
And I log in to a new session 14.509
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.580
And I plug USB drive "to_upgrade" 2.357
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.136
Then the running Tails is installed on USB drive "to_upgrade" 18.427
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:331 0.793
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.644
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.713
Then all tps features from the old Tails version are active 1.188
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 2.732
And the expected persistent files created with the old Tails version are present in the filesystem 1.217
And all persistent directories from the old Tails version have safe access rights 2.380
After features/support/hooks.rb:331 0.811
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
4:4.897
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 9.310
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
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.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.370
When the network is plugged 0.016
And Tor is ready 15.504
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.653
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.492
Given I shutdown Tails and wait for the computer to power off 10.048
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.562
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.610
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# 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.217
When the network is plugged 0.018
And Tor is ready 12.110
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.068
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.725
Given I shutdown Tails and wait for the computer to power off 4.708
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.090
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.314
And the file system changes introduced in version 6.3~testoverlayfs are present 0.392
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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.014
And Tor is ready 12.225
Then the Upgrader considers the system as up-to-date 10.726
# 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.525
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.583
After features/support/hooks.rb:331 1.233
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
21.653
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 8.206
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
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.044
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.782
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.326
After features/support/hooks.rb:331 0.645
After features/support/hooks.rb:100 0.000