This page explains how to connect to environments that cannot be accessed from the Internet, such as in-company environments, and conduct tests.
When running tests on a local PC
In this case, no special setup is required. As the browser and device are on the local PC, you can connect directly to the in-company environment.
When running tests on a Cloud device
When a MagicPod iOS/Android Cloud device accesses external environments, it uses the IP ranges 126.96.36.199/27 and 188.8.131.52/25. You can avoid the issue by permitting these IP address ranges on the in-company server or in the firewall settings.
*However, with this method, you will need to authenticate separately on the in-company server side, since the firewall will also allow access from other apps installed in the MagicPod cloud. If you are using the Enterprise Plan, however, you can pay for a dedicated connection source IP address to be used by the Cloud device. See here or inquire for details. Also, if you are using an environment that does not have a global IP address and can only be accessed from within the company, you can use cloud devices by combining them with dedicated client software. For more details, please click here.
When running tests on a Cloud browser
When a MagicPod Cloud browser accesses external environments, it uses the IP 184.108.40.206. You can avoid any issues by permitting this IP address range on the in-company Server or in the firewall settings.
*Restrictions here are the same as described above in the case of the Cloud device.
When running tests on BrowserStack
BrowserStack Local is a tool provided by BrowserStack that can be used to allow secure connections to private environments. Specifically, you can run BrowserStack Local on any machine that is able to connect to the intended private environment (this can even be on a different PC than the one on which you start the test run) and then set up MagicPod to use BrowserStack Local when running the test.
First, download the BrowserStack command-line tool corresponding to the OS of the machine on which BrowserStack Local is launched, from the Releases and Downloads.
After downloading it, use the BrowserStack access key and run the following command to start BrowserStack Local (on Windows) (BrowserStack Local is not a Server but a client that allows for bi-directional communication via WebSocket. Thus, it is usually not necessary to use port permission settings).
BrowserStackLocal.exe --key BrowserStack access key --force-local
In this state, if the test is run with the BrowserStack Local setting in the test batch execution set to Use self-launched instance, the test for the private environment will be run via BrowserStack Local. (The BrowserStack access key specified in the MagicPod settings should be the same as the one specified for BrowserStack Local. )
- For command-line execution with Web API or the magicpod-command-line, you can choose to run BrowserStack Local only during test execution, or keep it running constantly in a private environment if you frequently run tests.
- When you want to run multiple instances of BrowserStack Local, and change the connection point based on the test, enter your preferred id, such as --local-identifier Test123, to distinguish between the BrowserStack Local in the BrowserStackLocal.exe parameters, and specify the same ID for the BrowserStack Local ID item in the MagicPod specifications.
- When accessing a private Server from the machine on which BrowerStack Local is launched, via a Proxy, set the BrowerStack Local options as necessary, referring to BrowserStack Local Help.
When running tests on the Remote TestKit
When a device on Remote TestKit accesses external environments, the IP address described here will be used, so you can avoid any issues by permitting this IP address on your in-company server or in the firewall settings.
*You should note, however, that doing this will also permit access from Remote TestKit devices used by other users.