Manage multiple connections

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 command-line interface.

Via command-line interface:

Establish each Local Testing connection using the --local-identifier flag, along with a unique connection name (for instance, Test 123).

Note: Not using the --local-identifier flag (for each Local Testing connection) will cut off the existing connection and create a new one.

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

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

After establishing Local Testing connections, make use of the local and localIdentifer option on executing your test suite. The params are explained below:

Example cURL request :

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
-X POST "https://api-cloud.browserstack.com/app-automate/xcuitest/build" \
-d '{"local": "true", "localIdentifier": "Test123", "devices": ["iPhone 8 Plus-11.0"], "app": "bs://f5L3azt9pLzE995f49376eb1fa3c284dc321f8d", "testSuite": "bs://6eb1fa3c284ddbe9971b2d1aee0d52943b9c081"}' \
-H "Content-Type: application/json"

Managing 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:

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

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

Related topics

• Manage your uploaded app or test suite using our 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.