Skip to main content
Transform your testing process with: Real Device Features, Company-wide Licences, & Test Observability

Multiple Local Testing Connections

You can test multiple forks and builds at the same time by setting up separate Local Testing connections for each.

To do this, use one of the following options:

If you are using the BrowserStack SDK, add the following snippet to your browserstack.yml file:

browserstack.yml
Copy icon Copy snippet

Add the following snippet to your test scripts:

bsLocalArgs.put("localIdentifier", "randomstring");
bs_local_args = { 'key': '<browserstack-accesskey>', 'localIdentifier': 'randomstring' }
bsLocalArgs.Add(new KeyValuePair<string, string>("localIdentifier", "randomstring"));
my %bs_local_args = ("key" => "<browserstack-accesskey>", "localIdentifier" => "randomstring");
bs_local_args = { "key": "<browserstack-accesskey>" , "localIdentifier": "randomstring"}
bs_local_args = { "key" => "<browserstack-accesskey>" , "localIdentifier" => "randomstring"}
my %bs_local_args = ("key" => "<browserstack-accesskey>", "localIdentifier" => "randomstring");

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.

Run the binary using the following command:

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

After establishing Local Testing connections, configure the test script to run through a specific connection. To do so, set the browserstack.localIdentifier capability in your test scripts and add the unique connection name as parameter.

caps.setCapability("browserstack.local", "true");
caps.setCapability("browserstack.localIdentifier", "Test123");
var capabilities = {
  'browserstack.local' : 'true',
  'browserstack.localIdentifier' : 'Test123'
}
caps.SetCapability("browserstack.local", "true");
caps.SetCapability("browserstack.localIdentifier", "Test123")
$caps['browserstack.local'] = "true";
$caps['browserstack.localIdentifier'] = "Test123";
caps['browserstack.local'] = True
caps['browserstack.localIdentifier'] = 'Test123'
caps['browserstack.local'] = 'true'
caps['browserstack.localIdentifier'] = 'Test123'
my $caps = {
  "browserstack.local" => "true",
  "browserstack.localIdentifier" => "Test123"
};

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 <other_params>

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

Is this page helping you?

Yes
No

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!

Talk to an Expert
Download Copy