Project Number Date
test_Tails_ISO_stable 6244 29 Mar 2026, 08:07

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:50.219 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:31.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.070
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.358
When I start Tails from USB drive "old" with network unplugged 1:12.637
Then the boot device has safe access rights 2.790
And Tails is running from USB drive "old" 0.272
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 3.574
After features/support/hooks.rb:100 0.033
Tags: @product
1:33.312
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 58.579
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 25.745
And I take note of which tps features are available 0.784
Then a Tails persistence partition exists on USB drive "old" 0.737
And I shutdown Tails and wait for the computer to power off 7.084
After features/support/hooks.rb:331 0.569
After features/support/hooks.rb:100 0.008
Tags: @product
1:26.849
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.079
Then Tails is running from USB drive "old" 0.251
And all tps features are active 1.068
When I write some files expected to persist 1.313
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.510
And all persistent directories from the old Tails version have safe access rights 2.046
And I take note of which tps features are available 0.220
And I shutdown Tails and wait for the computer to power off 4.240
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.856
After features/support/hooks.rb:331 0.455
After features/support/hooks.rb:100 0.006
Tags: @product
2:21.998
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 without a persistent partition and stopped at Tails Greeter's login screen 8.452
And I log in to a new session 15.928
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.995
And I plug USB drive "to_upgrade" 2.280
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.204
Then the running Tails is installed on USB drive "to_upgrade" 16.803
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:331 3.775
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.693
Then all tps features from the old Tails version are active 1.085
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 2.417
And the expected persistent files created with the old Tails version are present in the filesystem 1.095
And all persistent directories from the old Tails version have safe access rights 1.910
After features/support/hooks.rb:331 0.731
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
5:11.873
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.913
And no SquashFS delta is installed 0.148
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.016
And Tor is ready 30.803
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.370
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.148
Given I shutdown Tails and wait for the computer to power off 20.841
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.006
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 1.377
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.202
When the network is plugged 0.016
And Tor is ready 20.335
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.473
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.074
Given I shutdown Tails and wait for the computer to power off 17.482
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.360
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.311
And the file system changes introduced in version 6.3~testoverlayfs are present 0.367
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.016
And Tor is ready 39.599
Then the Upgrader considers the system as up-to-date 0.137
# 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.430
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.402
After features/support/hooks.rb:331 0.813
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
30.999
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.807
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 22.388
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.380
After features/support/hooks.rb:331 0.908
After features/support/hooks.rb:100 0.000