Project Number Date
test_Tails_ISO_devel 4322 06 Apr 2026, 15:11

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:37.291 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:8.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.308
When I start Tails from USB drive "old" with network unplugged 51.488
Then the boot device has safe access rights 2.483
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 1.361
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.402
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 52.150
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 22.819
And I take note of which tps features are available 0.675
Then a Tails persistence partition exists on USB drive "old" 0.524
And I shutdown Tails and wait for the computer to power off 7.914
After features/support/hooks.rb:331 0.463
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.964
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.656
Then Tails is running from USB drive "old" 0.211
And all tps features are active 1.137
When I write some files expected to persist 1.155
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 1.907
And I take note of which tps features are available 0.204
And I shutdown Tails and wait for the computer to power off 7.818
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.158
After features/support/hooks.rb:331 0.387
After features/support/hooks.rb:100 0.007
Tags: @product
2:41.501
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.145
And I log in to a new session 32.808
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.826
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.764
Then the running Tails is installed on USB drive "to_upgrade" 15.393
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:331 13.891
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.295
Then all tps features from the old Tails version are active 0.955
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.450
And the expected persistent files created with the old Tails version are present in the filesystem 1.175
And all persistent directories from the old Tails version have safe access rights 1.778
After features/support/hooks.rb:331 0.805
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:59.701
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.399
And no SquashFS delta is installed 0.316
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.137
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.017
And Tor is ready 28.357
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.414
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.024
Given I shutdown Tails and wait for the computer to power off 22.053
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.485
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.028
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.205
When the network is plugged 0.014
And Tor is ready 21.691
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.362
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.344
Given I shutdown Tails and wait for the computer to power off 13.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.351
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.131
And the file system changes introduced in version 6.3~testoverlayfs are present 0.370
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.014
And Tor is ready 41.397
Then the Upgrader considers the system as up-to-date 0.101
# 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.284
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:331 0.854
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
48.800
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.572
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
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.017
And Tor is ready 40.235
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.543
After features/support/hooks.rb:331 1.031
After features/support/hooks.rb:100 0.000