Previous Topic

Next Topic

Book Contents

Book Index

Understand the Use Cases

In This Chapter

Tailor NeoLoad to your applications

Extend NeoLoad load testing capabilities

Extend NeoLoad monitoring capabilities

See Also

How to extend NeoLoad capacities using Custom Advanced Actions

Set up the environment for Advanced actions

Use Case 1: Handling an MD5 authentication

Use Case 2: Load testing a non-http protocol

Use Case 3: Sending my load test data to a third-party tool

Tailor NeoLoad to your applications

The behavior of your User Paths can be customized using NeoLoad Logical actions. For more information, see Logical actions. Some specific applications will require more complex algorithms (MD5 Hash on a password to login on a website, thick clients …). Those cases can be handled:

The first use case will guide you into using the Advanced Actions API to handle an MD5 Hash. For more information see Use case 1: Handling an MD5 authentication.

Extend NeoLoad load testing capabilities

NeoLoad can record any HTTP-based application. Of course, this also applies to other protocols that rely on HTTP (HTTPS, SOAP, etc.). While recording is not possible for other protocols, we can still use the NeoLoad Advanced Actions API to reproduce the communication with the application under test. Combining that with the NeoLoad load generation engine, any protocol can thus be load tested.

The second use case of this tutorial (Use case 2: Load testing a non-http protocol) will teach you how to develop your own custom protocols so that you can load test any application.

Extend NeoLoad monitoring capabilities

NeoLoad can monitor a good number of technologies as described in Monitors. When you cannot find what you are looking for in the built-in capabilities of the tool, you can use the Advanced Actions API to retrieve monitoring data from third-party tools. This process is detailed in Use case 3: Sending my load test data to a third party tool.