The Sauce Labs Cookbook

Sauce Headless

Front End Performance Testing

Insights

External Resources

More Info


Page tree
Skip to end of metadata
Go to start of metadata

The diagrams below illustrate common configuration mistakes that result in dysfunctional setups. Make sure to avoid these when setting up Sauce Connect!

See the following sections for more information:

Dysfunctional Geographic Domain Configuration

The problem with this network configuration is that the SC Host is in the same VPN – thus, the same internal network – as the Site Under Test (SUT), but they live in separate geographic locations. 

For example, if an SC Host is in Berlin and the SUT is located in a data center in Chicago, the connection would require a number of network hops, which would delay communication with the test virtual machine at Sauce Labs. This means that requests from Sauce Connect to the SUT would need to reach back through the internet to be completed, rather than over the same internal network.

The way to prevent this – a critical step in setting up Sauce Connect – is to ensure the SC Host is placed in the same geographic domain as the SUT.

DIAGRAM: Dysfunctional Geographic Domain Configuration

Diagram Legend

Term

Definition

SC Host (Sauce Connect Host)Machine in your network on which the Sauce Connect application is running.
SUT (Site Under Test)The site that you're testing.
Tunnel VM (Tunnel Virtual Machine)

Virtual machine that hosts Sauce Connect on the Sauce Labs side.

Dysfunctional DMZ + SUT Network Configuration

Another common mistake is placing the SUT in the same network as the Demilitarized Zone (DMZ). It's exposed to the internet, but isolated from the internal network.

DIAGRAM: SUT in Network DMZ

Diagram Legend

Term

Definition

SC Host (Sauce Connect Host)Machine in your network on which the Sauce Connect application is running.
SUT (Site Under Test)The site that you're testing.
Tunnel VM (Tunnel Virtual Machine)

Virtual machine that hosts Sauce Connect on the Sauce Labs side.