Test websites hosted on your private networks using the Local testing feature of BrowserStack
This page introduces you to the concept of Local Testing and explains how it works so that remote browsers and devices from the BrowserStack cloud can access websites hosted on your internal networks which are otherwise not accessible over the public Internet.
Now that your Local testing connection has been set up, this section explains how the different steps in a test are executed using the entire architecture. The following data flow diagram depicts the test execution flow:
Host machine makes a call to BrowserStack backend, requesting to start a session
Backend allocates an appropriate device as per requested capabilities, and asks the device to use the repeater as a proxy.
Backend informs the repeater regarding the device allocated to the session, and asks it to allow the allocated device to use it as a proxy.
Devices start making all network calls via the repeater
Repeater checks if the request can be resolved via the public Internet, or if it needs access to your private network. Note that this can be disabled with our force-local modifier, making everything go through your network mandatorily.
Repeater tries to resolve the request via the Local Agent running in your network.
Local Agent, which is running in your network and can reach your application servers, passes on and resolves the request.
We have seen how BrowserStack Local works and how you can use it to test websites hosted on your private networks. In simple scenarios, the above information should be enough to configure your setup but there are some advanced use-cases which might need some additional configurations.
The following links would guide you to proper resources that you might need to configure your Local testing setup satisfactorily:
Don’t see the language or framework you use? You can still run your tests. Contact Support for help.