Manage multiple local connections for Playwright

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

browserStackLocalOptions:
  localIdentifier: Test123

If you are using the browserstack-local node package, pass a unique localIdentifier while starting each Local instance:

const BS_LOCAL_ARGS = {
    'key': process.env.BROWSERSTACK_ACCESS_KEY || 'YOUR_ACCESS_KEY',
    'localIdentifier': 'Test123'
};
bsLocal.start(BS_LOCAL_ARGS, testFn);  // testFn is the actual function that contains the test

Then set the matching browserstack.localIdentifier capability in your test script:

const caps = {
    // ... other capabilities
    'browserstack.local': 'true',
    'browserstack.localIdentifier': 'Test123'
};

You can read more about specifying different flags in the arguments of the method call for creating the connection using the node package.

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

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 a parameter.