When developing web services and applications, it is a common practice to implement the interim work-in-progress versions of these services in local environments. Usually, such environments are somehow restricted from the global network to prevent unwanted external access from outside the organization.
To test performance of web resources in the local network, use LoadNinja private proxy, a lightweight desktop application. With this proxy, LoadNinja virtual users can access services and applications in your company’s intranet.
Operating system:
For Windows and Linux: An SSE2-capable Intel Pentium 4 processor or higher.
160 MB of free disk space.
Log in to LoadNinja.
Go to > Settings > Proxy.
Download the installation package for your operating system:
Click the image to enlarge it.
Locate the application on your device and run it.
In the subsequent authentication dialog, enter the email address and password of your LoadNinja account.
Click the image to enlarge it.
Click Connect.
If everything is OK, the application will show Connected.
Click the image to enlarge it.
You can then minimize the application and leave it running in the background.
Notes:
Depending on your operating system, you may have to permit the application to access the Internet.
To command the LoadNinja proxy service to connect to the Internet via another proxy, select Connect using proxy on the application’s main screen, then specify the connection data – the address, port, username, and password.
Open LoadNinja.
Go to > Settings > Proxy.
Check the Proxy Status panel there – it should show the Proxy is ON message.
Click the image to enlarge it.
Record a web test as usual.
In LoadNinja, go to the scenario creation form.
Add a web test you have recorded against the local service.
Add up to 15 virtual users.
To perform load tests on local applications with more than 15 virtual users involved, select the Initiate servers before starting the load test check box on the scenario creation form. After that, you will see the IP addresses of all the load generating instances before the test run starts. Modify your firewall rules to allow these instances to interact with your service, or contact your network administration team for assistance.
Specify the remaining settings as needed.
Launch the test as usual.
