Network Tunneling allows testers and developers to access a web/application server running on their own machine (Mac, Linux or Windows), from a cloud device (Android or iOS).
Network Tunneling allows testers & developers to access a web/application server running on their own machine (Mac, Linux or
Windows), from a cloud device (Android or iOS) or browsers.
Generally, Tunneling allows a Cloud Device or browsers to access any web resources on the developer's internal network, even if there is no direct connectivity between the two.
Tunneling is most useful when the remote
cloud and the developer machine are on distinct networks
that are not normally reachable from each other due to network topology or firewall configurations.
The Tunneling Client is a standalone program that when running, maintains a network tunnel between the developer machine and the Cloud.
The client is called network-tunnel on the Mac or Linux, and network-tunnel.exe on Windows.
Once a tunneling client is successfully connected to the Cloud Server, the invoking user (for a specific project, dictated by the Access Key) is considered to be in "Tunneling Mode". In this mode, all on-going sessions will have tunneled networking, and the device or browser can access network resources located on the developer's private network.
Like any user, in order to use tunneling during a Manual or Automation session, do the following:
- Open a session on the device you want to tunnel.
- Download and run the tunneling client on your
- Tunneling will be able to operate as long as the client is running and connected to the cloud.
- To stop tunneling, close the client.
For as long as a session is being tunneled, the web UI indicates it with a "Tunneling" icon on the left side of the screen:
System Requirements for tunneling client
The Windows client is compatible with Windows 10 and above.
The macOS client is compatible with macOS Catalina and above.
The Linux client is compatible with Linux RHEL/CentOS.