Project Number Date
test_Tails_ISO_stable 6312 20 Apr 2026, 14:25

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 13:7.621 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:14.077
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.516
When I start Tails from USB drive "old" with network unplugged 54.551
Then the boot device has safe access rights 3.074
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 3.572
After features/support/hooks.rb:100 0.019
Tags: @product
1:31.497
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 57.558
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 25.154
And I take note of which tps features are available 0.713
Then a Tails persistence partition exists on USB drive "old" 0.615
And I shutdown Tails and wait for the computer to power off 7.037
After features/support/hooks.rb:331 0.372
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.037
Then Tails is running from USB drive "old" 0.293
And all tps features are active 1.221
When I write some files expected to persist 1.260
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.500
And all persistent directories from the old Tails version have safe access rights 1.900
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 8.016
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.576
After features/support/hooks.rb:331 0.138
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.386
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.505
And I log in to a new session 12.881
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.860
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.914
Then the running Tails is installed on USB drive "to_upgrade" 17.684
And I unplug USB drive "to_upgrade" 0.169
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 1.955
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.135
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.699
Then all tps features from the old Tails version are active 1.128
And Tails is running from USB drive "to_upgrade" 0.486
And the boot device has safe access rights 3.122
And the expected persistent files created with the old Tails version are present in the filesystem 1.391
And all persistent directories from the old Tails version have safe access rights 2.231
After features/support/hooks.rb:331 0.792
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
4:51.720
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 8.874
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
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.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.403
When the network is plugged 0.016
And Tor is ready 20.598
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.375
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.257
Given I shutdown Tails and wait for the computer to power off 20.871
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.896
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.352
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.221
When the network is plugged 0.014
And Tor is ready 22.057
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.445
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.594
Given I shutdown Tails and wait for the computer to power off 17.708
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.934
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.274
And the file system changes introduced in version 6.3~testoverlayfs are present 0.390
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.018
And Tor is ready 22.608
Then the Upgrader considers the system as up-to-date 0.097
# 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.700
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.439
After features/support/hooks.rb:331 0.939
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
28.578
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 8.313
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 19.465
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.389
After features/support/hooks.rb:331 0.871
After features/support/hooks.rb:100 0.000