Project Number Date
test_Tails_ISO_stable 6133 10 Feb 2026, 12:02

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:57.644 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:53.842
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.887
When I start Tails from USB drive "old" with network unplugged 1:35.323
Then the boot device has safe access rights 2.607
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.143
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:331 1.696
After features/support/hooks.rb:100 0.006
Tags: @product
1:33.238
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 1:4.071
Then Tails is running from USB drive "old" 0.266
And I create a persistent partition 24.909
And I take note of which tps features are available 0.687
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 2.674
After features/support/hooks.rb:331 0.197
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.529
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.859
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.159
When I write some files expected to persist 1.302
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.281
And all persistent directories from the old Tails version have safe access rights 2.130
And I take note of which tps features are available 0.185
And I shutdown Tails and wait for the computer to power off 8.164
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.917
After features/support/hooks.rb:331 0.348
After features/support/hooks.rb:100 0.008
Tags: @product
2:23.843
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 8.689
And I log in to a new session 14.525
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.697
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.746
Then the running Tails is installed on USB drive "to_upgrade" 16.666
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:331 3.493
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.747
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.895
Then all tps features from the old Tails version are active 1.456
And Tails is running from USB drive "to_upgrade" 0.263
And the boot device has safe access rights 2.760
And the expected persistent files created with the old Tails version are present in the filesystem 1.168
And all persistent directories from the old Tails version have safe access rights 2.148
After features/support/hooks.rb:331 1.026
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:1.736
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.397
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.016
And Tor is ready 16.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.238
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.889
Given I shutdown Tails and wait for the computer to power off 20.954
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.426
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.192
And the file system changes introduced in version 6.2~testoverlayfs are present 0.199
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.188
When the network is plugged 0.016
And Tor is ready 11.664
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.884
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.453
Given I shutdown Tails and wait for the computer to power off 7.994
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.552
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.355
And the file system changes introduced in version 6.3~testoverlayfs are present 0.406
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.214
When the network is plugged 0.020
And Tor is ready 10.198
Then the Upgrader considers the system as up-to-date 10.607
# 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.326
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.445
After features/support/hooks.rb:331 0.773
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
20.707
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.565
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.424
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.416
After features/support/hooks.rb:331 1.030
After features/support/hooks.rb:100 0.000