More than one tunnel, in parallel

Your account supports up to 2 simultaneous tunnels. They can be tunnels you start yourself or shared tunnels from team members on the same account.

Why use multiple tunnels?

Parallel

Higher throughput

Spread test traffic across tunnels for higher throughput.

High availability

Run tunnels on different machines for redundancy.

Isolate

Environment isolation

Dedicate one tunnel per environment (staging, QA, dev).

Team

Team workflows

Let team members run tunnels for their own tests without conflicts.

Setting up tunnel identifiers

Use the --tunnel-identifier flag to give each tunnel a unique name.

java -jar testingbot-tunnel.jar key secret --tunnel-identifier myTunnel

Then specify the identifier in the desired capabilities of each test that should be routed through that tunnel:

{
  "browserName": "firefox",
  "browserVersion": "latest",
  "platformName": "WIN11",
  "tunnel-identifier": "myTunnel"
}

Parallel test isolation

When two test suites both rely on the tunnel (for example a staging suite and a QA suite), give each suite its own tunnel and identifier. This prevents one suite from saturating the other's bandwidth and makes monitoring per-suite traffic straightforward via the metrics endpoint.

High availability

Run identically-configured tunnels on two or more machines using the same identifier. The TestingBot grid load-balances test traffic across all available tunnels with that identifier and routes around any tunnel that becomes unhealthy.