Ask the Community
Set up multiple Local Testing connections for Detox tests
Run Detox tests across multiple forks and builds at once by setting up separate Local Testing connections for each.
You can test multiple forks and builds at the same time by setting up separate Local Testing connections for each. To do so, establish Local Testing connections using one of two ways:
Via command-line interface
Establish each Local Testing connection using the --local-identifier flag, along with a unique connection name (for instance, Test123).
If you don’t use the --local-identifier flag for each Local Testing connection, the existing connection is cut off and a new one is created.
After establishing Local Testing connections, make use of the local and localIdentifier option on executing your test suite. The params are explained below:
| Parameter | Description | Values |
|---|---|---|
| local | Set this parameter if you want to enable Local Testing. | true/ false Default: false |
| localIdentifier | Set this parameter, if you are using the same account to test multiple applications. It helps to set up a named connection. | string Example: Test123 |
Example:
Manage multiple Local Testing connections
You can use the Local Testing API to check the status of (or disconnect) active binaries. However, your connections will not show up in the API response unless you establish them using --enable-logging-for-api flag, as follows:
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!