Set up multiple Local Testing connections for Flutter tests

Run Flutter integration tests across multiple forks and builds at once by setting up a separate Local Testing connection for each.

You can test multiple forks and builds at the same time by setting up a separate Local Testing connection for each one. Each connection needs its own name so that BrowserStack routes every build through the right tunnel.

Establish named connections

Establish each Local Testing connection using the --local-identifier flag, along with a unique connection name such as Test123:

After you establish the connections, use the local and localIdentifier parameters when you execute a build. The following table describes both parameters:

The following request runs a build through the connection named Test123:

Monitor multiple connections

Use the Local Testing API to check the status of active binaries or to disconnect them. Your connections don’t appear in the API response unless you establish them with the --enable-logging-for-api flag:

For the available endpoints, see Manage Local binary instances for Flutter tests.