Project Number Date
test_Tails_ISO_devel 4058 06 Nov 2025, 14:01

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 16:11.229 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:47.725
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.038
And I write an old version of the Tails USB image to disk "old" 32.472
When I start Tails from USB drive "old" with network unplugged 1:10.393
Then the boot device has safe access rights 2.703
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:331 5.826
After features/support/hooks.rb:100 0.121
Tags: @product
2:0.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.164
Given a computer 0.570
And I start Tails from USB drive "old" with network unplugged and I login 1:23.035
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 27.034
And I take note of which tps features are available 1.072
Then a Tails persistence partition exists on USB drive "old" 0.619
And I shutdown Tails and wait for the computer to power off 7.752
After features/support/hooks.rb:331 0.497
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.963
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.084
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.032
When I write some files expected to persist 1.574
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.400
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 7.562
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.692
After features/support/hooks.rb:331 0.498
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.628
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 13.185
And I log in to a new session 17.510
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.335
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.172
Then the running Tails is installed on USB drive "to_upgrade" 19.546
And I unplug USB drive "to_upgrade" 0.240
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:331 3.862
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.711
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.229
Then all tps features from the old Tails version are active 3.510
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 2.818
And the expected persistent files created with the old Tails version are present in the filesystem 1.345
And all persistent directories from the old Tails version have safe access rights 2.344
After features/support/hooks.rb:331 0.733
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:26.528
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 12.582
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.054
And Tor is ready 42.511
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.592
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.620
Given I shutdown Tails and wait for the computer to power off 8.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.535
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.017
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.245
When the network is plugged 0.057
And Tor is ready 12.243
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.619
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.470
Given I shutdown Tails and wait for the computer to power off 7.720
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:36.142
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.225
And the file system changes introduced in version 6.3~testoverlayfs are present 0.504
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.174
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.058
And Tor is ready 12.657
Then the Upgrader considers the system as up-to-date 0.228
# 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 6.425
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.555
After features/support/hooks.rb:331 1.315
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
26.250
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 12.832
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 12.428
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.609
After features/support/hooks.rb:331 1.097
After features/support/hooks.rb:100 0.000