Project Number Date
test_Tails_ISO_stable 6263 05 Apr 2026, 07:26

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:34.709 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
2:6.967
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.626
When I start Tails from USB drive "old" with network unplugged 1:48.982
Then the boot device has safe access rights 2.648
And Tails is running from USB drive "old" 0.193
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.793
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.621
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 54.022
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 23.149
And I take note of which tps features are available 0.696
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 7.841
After features/support/hooks.rb:331 0.303
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.600
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.297
Then Tails is running from USB drive "old" 0.237
And all tps features are active 1.060
When I write some files expected to persist 1.218
# 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.460
And all persistent directories from the old Tails version have safe access rights 1.712
And I take note of which tps features are available 0.133
And I shutdown Tails and wait for the computer to power off 8.107
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.148
After features/support/hooks.rb:331 0.279
After features/support/hooks.rb:100 0.006
Tags: @product
2:37.027
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.815
And I log in to a new session 26.215
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.758
And I plug USB drive "to_upgrade" 2.195
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.164
Then the running Tails is installed on USB drive "to_upgrade" 15.618
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:331 1.384
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.122
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.152
Then all tps features from the old Tails version are active 1.195
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.654
And the expected persistent files created with the old Tails version are present in the filesystem 1.004
And all persistent directories from the old Tails version have safe access rights 1.845
After features/support/hooks.rb:331 0.601
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:24.795
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.203
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.387
When the network is plugged 0.022
And Tor is ready 23.354
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.435
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.269
Given I shutdown Tails and wait for the computer to power off 20.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.267
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.062
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.181
When the network is plugged 0.021
And Tor is ready 20.136
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.353
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.875
Given I shutdown Tails and wait for the computer to power off 17.095
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.051
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.237
And the file system changes introduced in version 6.3~testoverlayfs are present 0.354
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.015
And Tor is ready 21.110
Then the Upgrader considers the system as up-to-date 0.123
# 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.228
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.364
After features/support/hooks.rb:331 0.731
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
27.573
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 with a persistent partition enabled and logged in 7.503
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 19.082
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.488
After features/support/hooks.rb:331 0.658
After features/support/hooks.rb:100 0.000