Project Number Date
test_Tails_ISO_devel 4122 15 Dec 2025, 12:35

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 15:25.281 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:52.325
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 39.798
When I start Tails from USB drive "old" with network unplugged 1:7.318
Then the boot device has safe access rights 3.059
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.236
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:331 4.326
After features/support/hooks.rb:100 0.011
Tags: @product
1:55.275
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:5.969
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 37.333
And I take note of which tps features are available 2.524
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 8.148
After features/support/hooks.rb:331 0.337
After features/support/hooks.rb:100 0.009
Tags: @product
2:1.123
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:25.914
Then Tails is running from USB drive "old" 0.691
And all tps features are active 2.208
When I write some files expected to persist 1.643
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 2.358
And I take note of which tps features are available 0.615
And I shutdown Tails and wait for the computer to power off 7.676
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.191
After features/support/hooks.rb:331 0.424
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.525
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.890
And I log in to a new session 18.629
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.430
And I plug USB drive "to_upgrade" 2.988
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.241
Then the running Tails is installed on USB drive "to_upgrade" 21.925
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:331 4.157
After features/support/hooks.rb:100 0.000
Tags: @product
1:34.910
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:25.804
Then all tps features from the old Tails version are active 2.034
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 2.887
And the expected persistent files created with the old Tails version are present in the filesystem 1.202
And all persistent directories from the old Tails version have safe access rights 2.454
After features/support/hooks.rb:331 1.084
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
4:54.428
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.467
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.059
And Tor is ready 14.795
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.069
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.421
Given I shutdown Tails and wait for the computer to power off 12.123
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.670
Then Tails is running version 6.2~testoverlayfs 0.114
And all tps features are active 2.250
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.244
# 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.264
When the network is plugged 0.058
And Tor is ready 12.104
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.871
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.732
Given I shutdown Tails and wait for the computer to power off 7.925
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.357
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.384
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.538
When the network is plugged 0.056
And Tor is ready 11.453
Then the Upgrader considers the system as up-to-date 10.780
# 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.869
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.546
After features/support/hooks.rb:331 0.930
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
25.692
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.281
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.108
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 11.996
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.735
After features/support/hooks.rb:331 0.756
After features/support/hooks.rb:100 0.000