Last updated
Was this helpful?
The testSynchronous attribute no longer has any effect. Nothing in sfp reads it to decide how tests run. It can be removed from sfdx-project.json.
Package tests during validation already run synchronously. Before running a package's tests, sfp turns off the org's parallel Apex testing setting, so every test in the package runs serially whether or not the attribute is present. This is why the attribute became redundant: the behaviour it used to request is now the only behaviour.
The --disableparalleltesting flag on sfp validate sets the same org switch, so it has no additional effect on this path either.
Tests that fail on row locks (UNABLE_TO_LOCK_ROW) are retried, which covers the failure mode that asynchronous execution used to cause.
Independent of validation, tests are triggered synchronously for source and diff packages during package installation. Unlocked and org-dependent unlocked packages do not trigger Apex tests during installation.
Last updated
Was this helpful?
Was this helpful?