Project Number Date
test_Tails_ISO_devel 4634 23 Sep 2026, 11:04

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 10:49.409 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
58.061
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.120
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 12.941
When I start Tails from USB drive "old" with network unplugged 41.331
Then the boot device has safe access rights 2.046
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.032
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.461
After features/support/hooks.rb:108 0.017
Tags: @product
1:20.389
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 46.521
Then Tails is running from USB drive "old" 0.193
And I create a persistent partition 23.190
And I take note of which tps features are available 5.930
Then a Tails persistence partition exists on USB drive "old" 0.462
And I shutdown Tails and wait for the computer to power off 4.013
After features/support/hooks.rb:339 0.437
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.981
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.578
Then Tails is running from USB drive "old" 0.186
And all tps features are active 6.872
When I write some files expected to persist 0.907
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.103
And all persistence configuration files have safe access rights 0.212
And all persistent directories from the old Tails version have safe access rights 1.350
And I take note of which tps features are available 6.204
And I shutdown Tails and wait for the computer to power off 2.529
# 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" 10.953
After features/support/hooks.rb:339 0.291
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.858
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.267
And I log in to a new session 10.856
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.650
And I plug USB drive "to_upgrade" 2.212
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.625
Then the running Tails is installed on USB drive "to_upgrade" 17.027
And I unplug USB drive "to_upgrade" 0.107
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 1.747
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.348
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.735
Then all tps features from the old Tails version are active 1.030
And Tails is running from USB drive "to_upgrade" 0.173
And the boot device has safe access rights 2.020
And the expected persistent files created with the old Tails version are present in the filesystem 0.911
And all persistent directories from the old Tails version have safe access rights 1.394
After features/support/hooks.rb:339 0.846
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:28.377
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.862
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.270
When the network is plugged 0.029
And Tor is ready 12.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.828
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.623
Given I shutdown Tails and wait for the computer to power off 5.186
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.349
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.256
And the file system changes introduced in version 6.2~testoverlayfs are present 0.195
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.080
# 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.170
When the network is plugged 0.033
And Tor is ready 10.321
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.437
Given I shutdown Tails and wait for the computer to power off 2.572
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.083
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 6.972
And the file system changes introduced in version 6.3~testoverlayfs are present 0.256
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.106
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.126
When the network is plugged 0.028
And Tor is ready 10.178
Then the Upgrader considers the system as up-to-date 10.417
# 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 3.237
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.321
After features/support/hooks.rb:339 0.946
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.391
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.799
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
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.031
And Tor is ready 10.165
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.091
After features/support/hooks.rb:339 0.811
After features/support/hooks.rb:108 0.000