Test on internal networks

Set up Local Testing to execute your test suites with localhost/private URL’s on cloud successfully.

BrowserStack Low Code Automation can trigger test suites against your local & staging websites, and even websites behind proxies/firewalls. This is done using BrowserStack Local - a tunneling capability that establishes a secure connection between the machine running the binary and BrowserStack Cloud.

If you have triggered a Test suite and have faced the below issue while accessing the build run, it’s likely because you do not have Local setup running.

Pre-requisite

You need to have BrowserStack Username and Access key, which you can find in your account settings. If you have not created an account yet, you can sign up for a Free Trial.

To enable local, follow the setup instructions mentioned below.

How to configure and setup Local Testing?

Step 1: Enable Local Testing for Test Suite

1. Navigate to the test suite which has tests recorded on local or internal staging website.
2. Edit the test suite and turn ON the setting Enable local testing.

Step 2: Setup Local Binary

Follow the setup instructions for your OS:

BrowserStackLocal.exe --key YOUR_ACCESS_KEY

./BrowserStackLocal --key YOUR_ACCESS_KEY

./BrowserStackLocal --key YOUR_ACCESS_KEY

Test websites behind a firewall or VPN

With Local Testing, you can test internally hosted websites that are behind a firewall and/or VPNs.

If your Website / VPN / Firewall / Proxy only accept connections from certain IP addresses or Subnet addresses then it is mandatory to enable “Force Local”. You can enable it in either of the following ways

1. If the binary is already running, navigate to http://localhost:45454, and toggle force local on.
2. Pass the force local flag directly while running the binary as shown below:
   • For Windows

     BrowserStackLocal.exe --key YOUR_ACCESS_KEY --force-local
     

   • For macOS/Linux

     ./BrowserStackLocal --key YOUR_ACCESS_KEY --force-local
     

To set up Local Testing for other environments/network configurations, refer to our complete list of flags.

Inbound IP Whitelisting

IP Whitelisting is a BrowserStack solution where, instead of doing resolution of local assets via the Binary, the BrowserStack cloud directly accesses your assets via a limited and secure set of machines whose IPs have been whitelisted by your network administrator. If you want the BrowserStack cloud to directly resolve your IP-restricted assets without passing through the Binary, you can use this solution.

Learn more about how IP Whitelisting works and its pre-requisites here.

Follow these steps to properly set up IP whitelisting for Low Code Automation:

1. Get in touch with our Support team to enable IP whitelisting.
2. After enabling the feature and whitelisting the IPs, activate the local setting for the test suites. Refer to Step 1 in the How to Configure and Set Up Local Testing? section.