Project Number Date
test_Tails_ISO_21322-change-domain-deb.tails.boum.org 1 18 May 2026, 19:38

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 11:41.340 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:10.986
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.420
When I start Tails from USB drive "old" with network unplugged 53.015
Then the boot device has safe access rights 2.599
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:335 1.460
After features/support/hooks.rb:104 0.008
Tags: @product
1:31.065
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 56.600
Then Tails is running from USB drive "old" 0.241
And I create a persistent partition 26.260
And I take note of which tps features are available 0.365
Then a Tails persistence partition exists on USB drive "old" 0.673
And I shutdown Tails and wait for the computer to power off 6.857
After features/support/hooks.rb:335 0.322
After features/support/hooks.rb:104 0.008
Tags: @product
1:29.417
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.116
Then Tails is running from USB drive "old" 0.259
And all tps features are active 1.091
When I write some files expected to persist 1.209
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 1.971
And I take note of which tps features are available 0.178
And I shutdown Tails and wait for the computer to power off 8.463
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.534
After features/support/hooks.rb:335 0.421
After features/support/hooks.rb:104 0.008
Tags: @product
2:12.694
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.648
And I log in to a new session 12.154
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.174
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.062
Then the running Tails is installed on USB drive "to_upgrade" 16.113
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:335 0.644
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.521
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.129
Then all tps features from the old Tails version are active 0.926
And Tails is running from USB drive "to_upgrade" 0.266
And the boot device has safe access rights 2.637
And the expected persistent files created with the old Tails version are present in the filesystem 1.299
And all persistent directories from the old Tails version have safe access rights 2.200
After features/support/hooks.rb:335 0.879
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:45.398
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.338
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.015
And Tor is ready 12.463
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.567
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.600
Given I shutdown Tails and wait for the computer to power off 11.198
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.202
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.294
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.194
When the network is plugged 0.024
And Tor is ready 11.209
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.861
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.402
Given I shutdown Tails and wait for the computer to power off 8.170
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.062
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.193
And the file system changes introduced in version 6.3~testoverlayfs are present 0.404
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.211
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.055
And Tor is ready 10.176
Then the Upgrader considers the system as up-to-date 10.547
# 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.254
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:335 0.948
After features/support/hooks.rb:104 0.019
Tags: @product @automatic_upgrade
20.256
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.392
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
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.017
And Tor is ready 10.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.873
After features/support/hooks.rb:335 0.953
After features/support/hooks.rb:104 0.000