Project Number Date
test_Tails_ISO_devel 4157 08 Jan 2026, 07:54

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:54.397 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.285
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.573
When I start Tails from USB drive "old" with network unplugged 51.234
Then the boot device has safe access rights 2.647
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.035
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 3.990
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.959
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 55.177
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 25.060
And I take note of which tps features are available 0.722
Then a Tails persistence partition exists on USB drive "old" 0.681
And I shutdown Tails and wait for the computer to power off 6.849
After features/support/hooks.rb:331 0.419
After features/support/hooks.rb:100 0.005
Tags: @product
1:27.849
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.077
Then Tails is running from USB drive "old" 0.273
And all tps features are active 1.047
When I write some files expected to persist 1.148
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.290
And all persistent directories from the old Tails version have safe access rights 1.981
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 8.593
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.035
After features/support/hooks.rb:331 0.458
After features/support/hooks.rb:100 0.005
Tags: @product
2:11.337
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 7.988
And I log in to a new session 12.720
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.601
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.444
Then the running Tails is installed on USB drive "to_upgrade" 16.035
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.165
After features/support/hooks.rb:331 3.878
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.871
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.522
Then all tps features from the old Tails version are active 0.950
And Tails is running from USB drive "to_upgrade" 0.284
And the boot device has safe access rights 2.656
And the expected persistent files created with the old Tails version are present in the filesystem 1.157
And all persistent directories from the old Tails version have safe access rights 2.248
After features/support/hooks.rb:331 0.846
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
3:39.555
Before features/support/hooks.rb:266 0.004
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.572
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.016
And Tor is ready 13.696
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.240
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.152
Given I shutdown Tails and wait for the computer to power off 9.786
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.893
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.270
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
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.119
# 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.196
When the network is plugged 0.019
And Tor is ready 9.957
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.505
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.880
Given I shutdown Tails and wait for the computer to power off 8.045
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.195
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.132
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.062
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.018
And Tor is ready 10.868
Then the Upgrader considers the system as up-to-date 10.675
# 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.776
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.516
After features/support/hooks.rb:331 0.954
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
48.538
Before features/support/hooks.rb:266 0.004
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.233
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 39.601
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.361
After features/support/hooks.rb:331 0.666
After features/support/hooks.rb:100 0.000