> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/sfp/validating-a-change/controlling-validation-attributes-of-a-package/test-synchronously.md).

# Test Synchronously

{% hint style="warning" %}
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`.
{% endhint %}

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.

## During installation

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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flxbl.io/flxbl/sfp/validating-a-change/controlling-validation-attributes-of-a-package/test-synchronously.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.