Test on Internal Networks

Run tests on internal networks and use tunnel connection for other advanced use-cases

TestCafe operates in a way that irrespective of the fact that you are testing a locally hosted website or a publicly available one, all traffic goes through your local machine which runs the TestCafe instance. Hence, BrowserStackLocal setup is mandatory as we have already seen in the section for setting up BrowserStack Local connection section.

You do not need to make any separate arrangements to run any locally hosted website. You can simply specify the localhost URL and your test should work fine. The next section addresses the concerns if you are behind a proxy.

Run tests from behind a proxy

If you are behind a proxy and want to run your tests on BrowserStack, you have to ensure that the BrowserStackLocal tunnel connection is established between your machine and the BrowserStack cloud. The following sections will help you achieve that.

User managed tunnel connection

You should have downloaded the appropriate BrowserStackLocal binary. If not, you can download from one of the links below:

• OSX
• Linux-32 bit
• Linux-64 bit
• Windows

You now have to start the binary with the proxy arguments as shown below:

./BrowserStackLocal --key YOUR_ACCESS_KEY --proxy-host HOST --proxy-port PORT --local-identifier TestCafe --daemon start --parallel-runs <number-of-parallels>

HOST and PORT should be replaced with the proxy hostname and respective port.

If your proxy requires basic authentication, use the invocation as shown below:

./BrowserStackLocal --key YOUR_ACCESS_KEY --proxy-host HOST --proxy-port PORT --proxy-user USERNAME --proxy-pass PASSWORD --local-identifier TestCafe --daemon start --parallel-runs <number-of-parallels>

You can also set the proxy details using a PAC file as shown below:

./BrowserStackLocal --key YOUR_ACCESS_KEY --pac-file PAC FILE PATH --local-identifier TestCafe --daemon start --parallel-runs <number-of-parallels>

See the complete list of supported local arguments which you can use in the local binary invocation

TestCafe managed tunnel connection

If you let TestCafe manage the BrowserStack tunnel connection then you have to set values for these environment variables if you are behind a proxy:

Example:

export BROWSERSTACK_PROXY="user:p@ssw0rd@proxy.com:8080"
export BROWSERSTACK_LOCAL_PROXY="admin:12345678@192.168.0.2:8080"
export BROWSERSTACK_FORCE_PROXY="1"
export BROWSERSTACK_FORCE_LOCAL="1"
testcafe browserstack:chrome test.js

Other options for TestCafe managed local

Setting these additional environment variables will let you avail more features of BrowserStackLocal binary as shown below:

Example:

export BROWSERSTACK_BINARY_PATH="~/BrowserStack/BrowserStackLocal"
export BROWSERSTACK_LOGFILE="~/BrowserStack/logs.txt"
export BROWSERSTACK_VERBOSE="1"
testcafe browserstack:chrome test.js