Manage incoming connections for Detox tests

Test Detox apps that fetch data from localhost, private, internal, or firewalled servers using Local Testing on BrowserStack App Automate.

When your Detox apps depend on data hosted inside your own network, Local Testing lets BrowserStack’s remote devices reach those servers securely. The following sections explain how to test apps that pull data from localhost servers, private or internal servers, and servers behind firewalls or VPNs, and how to manage the connection’s lifecycle.

Test apps that retrieve data from localhost servers

Once you’ve enabled Local Testing, our remote devices will be able to access apps that retrieve data from your localhost servers. Use your test scripts to access and interact with your apps. Remember to use the local parameter when executing the test:

Test apps that retrieve data from private or internal servers

You can securely test mobile apps that retrieve data from private or internal servers using --force-local on our remote mobile devices. This option resolves all requests (on our remote devices) through your local machine.

To enable this option, use one of two ways to establish the Local Testing connection:

Via command-line interface:

Use the --force-local flag while establishing a Local Testing connection.

After establishing the Local Testing connection, use your test scripts to access and interact with your internally hosted website (for example, staging.example.com).

Test apps that retrieve data from servers behind a firewall, a VPN, or both

With Local Testing, you can test apps that retrieve data or assets from internal servers that are behind firewalls, VPNs, or both.

Start by making sure that you can access the app on your machine. Then, set up a Local Testing connection by following the steps in Test apps that retrieve data from private or internal servers.

Connection duration and disconnection

The Local Testing connection is persistent. Your machine and BrowserStack Cloud remain connected unless you explicitly end the connection. In the following scenarios, ensure that you open and close the connection by following the steps: