Setup multiple local connections for XCUI tests

Manage multiple local testing connections for testing apps that retrieve data from servers on your local machine, CI/CD machines/nodes, and other private network configurations.

You can test multiple forks and builds at the same time by setting up separate Local Testing connections for each. To do so, establish each Local Testing connection using the --local-identifier flag, along with a unique connection name (for instance, Test123).

./BrowserStackLocal --key YOUR_ACCESS_KEY --local-identifier Test123

BrowserStackLocal.exe --key YOUR_ACCESS_KEY --local-identifier Test123

After establishing Local Testing connections, use the local and localIdentifier parameters when executing your build. The parameters are explained below:

Example cURL request:

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 the --enable-logging-for-api flag, as follows:

./BrowserStackLocal --key YOUR_ACCESS_KEY --enable-logging-for-api

BrowserStackLocal.exe --key YOUR_ACCESS_KEY --enable-logging-for-api

For the available endpoints, see Manage Local binary instances.

Related topics

• Manage your uploaded app or test suite using the upload app REST API and upload test suite REST API..

• Use the get app API endpoint and list test suites API endpoint to list your recently uploaded apps and test suites.

• Delete your uploaded app or test suite using the delete app API endpoint and delete test suite API endpoint.