Project Number Date
test_Tails_ISO_stable 6107 30 Jan 2026, 12:43

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:12.704 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:54.141
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.730
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 36.719
When I start Tails from USB drive "old" with network unplugged 1:11.074
Then the boot device has safe access rights 3.663
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.233
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:331 3.907
After features/support/hooks.rb:100 0.008
Tags: @product
1:52.740
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:9.571
Then Tails is running from USB drive "old" 0.622
And I create a persistent partition 32.619
And I take note of which tps features are available 1.265
Then a Tails persistence partition exists on USB drive "old" 0.742
And I shutdown Tails and wait for the computer to power off 7.723
After features/support/hooks.rb:331 0.322
After features/support/hooks.rb:100 0.010
Tags: @product
1:56.422
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:20.183
Then Tails is running from USB drive "old" 0.278
And all tps features are active 1.957
When I write some files expected to persist 2.399
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.267
And all persistence configuration files have safe access rights 0.466
And all persistent directories from the old Tails version have safe access rights 2.721
And I take note of which tps features are available 0.465
And I shutdown Tails and wait for the computer to power off 4.933
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 22.545
After features/support/hooks.rb:331 0.598
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.064
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 14.723
And I log in to a new session 15.420
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.590
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.883
Then the running Tails is installed on USB drive "to_upgrade" 22.525
And I unplug USB drive "to_upgrade" 0.288
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:331 4.287
After features/support/hooks.rb:100 0.000
Tags: @product
1:34.847
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.114
Given a computer 1.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:24.516
Then all tps features from the old Tails version are active 1.745
And Tails is running from USB drive "to_upgrade" 0.414
And the boot device has safe access rights 3.325
And the expected persistent files created with the old Tails version are present in the filesystem 1.260
And all persistent directories from the old Tails version have safe access rights 2.397
After features/support/hooks.rb:331 1.027
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:47.578
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 14.016
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
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.498
When the network is plugged 0.050
And Tor is ready 15.025
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.932
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.845
Given I shutdown Tails and wait for the computer to power off 11.883
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:29.687
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 3.213
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.212
# 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.277
When the network is plugged 0.056
And Tor is ready 13.841
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.720
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.228
Given I shutdown Tails and wait for the computer to power off 9.654
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.120
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 3.927
And the file system changes introduced in version 6.3~testoverlayfs are present 0.922
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.202
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.067
And Tor is ready 13.552
Then the Upgrader considers the system as up-to-date 0.157
# 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 7.375
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.606
After features/support/hooks.rb:331 1.405
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
23.908
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 11.041
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.122
And Tor is ready 10.552
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.777
After features/support/hooks.rb:331 1.233
After features/support/hooks.rb:100 0.000