Project Number Date
test_Tails_ISO_21322-change-domain-deb.tails.boum.org 37 22 Jun 2026, 08:05

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:27.018 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:15.637
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.038
Given a computer 0.127
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 14.398
When I start Tails from USB drive "old" with network unplugged 56.155
Then the boot device has safe access rights 3.005
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.400
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:339 3.704
After features/support/hooks.rb:108 0.024
Tags: @product
1:34.464
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.022
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login 56.701
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 25.397
And I take note of which tps features are available 4.441
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 6.918
After features/support/hooks.rb:339 0.417
After features/support/hooks.rb:108 0.017
Tags: @product
1:41.009
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.484
Then Tails is running from USB drive "old" 0.256
And all tps features are active 5.150
When I write some files expected to persist 1.469
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.084
And I take note of which tps features are available 5.007
And I shutdown Tails and wait for the computer to power off 6.983
# 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.834
After features/support/hooks.rb:339 0.400
After features/support/hooks.rb:108 0.019
Tags: @product
2:13.865
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.826
And I log in to a new session 14.284
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.830
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.319
Then the running Tails is installed on USB drive "to_upgrade" 15.041
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:339 2.736
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.259
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.635
Then all tps features from the old Tails version are active 1.041
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.841
And the expected persistent files created with the old Tails version are present in the filesystem 1.289
And all persistent directories from the old Tails version have safe access rights 2.030
After features/support/hooks.rb:339 0.968
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
4:3.468
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.776
And no SquashFS delta is installed 0.108
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.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 0.014
And Tor is ready 12.583
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.208
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.778
Given I shutdown Tails and wait for the computer to power off 10.164
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.908
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.188
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# 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.209
When the network is plugged 0.015
And Tor is ready 10.220
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.931
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.970
Given I shutdown Tails and wait for the computer to power off 8.702
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.853
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.128
And the file system changes introduced in version 6.3~testoverlayfs are present 0.405
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.014
And Tor is ready 9.730
Then the Upgrader considers the system as up-to-date 10.716
# 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 5.316
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.511
After features/support/hooks.rb:339 0.976
After features/support/hooks.rb:108 0.037
Tags: @product @automatic_upgrade
21.313
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.039
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.227
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.571
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.207
After features/support/hooks.rb:339 0.905
After features/support/hooks.rb:108 0.000