NeoLoad is an enterprise tool for performance and load testing, covering both API and end-to-end application testing.
Besides support for web-based applications, it also supports a broader set of applications and protocols, including SAP, Oracle Forms, Adobe Flex, etc.
Users may define SLA's based on performance metrics, giving them insights about performance that can be crucial for business.
Performance tests can be triggered manually (e.g. from within NeoLoad GUI or NeoLoad web) or from a CI/CD pipeline.
This integration provides the ability to track performance & load testing results in Xray, thus making it the single source of truth for tracking different testing efforts.
It provides:
In NeoLoad, all happens in the context of a working project, which may be created/modified using NeoLoad GUI.
A project contains one or more (test) scenarios. Each scenario has a set of user paths (i.e. flows) to be exercised along with the running conditions (e.g. duration, load policy, VUs).
A user path corresponds to the definition of a browsing sequence in the target application; it contains, for example, the HTTP requests to be performed.
Optionally, users can define one or more SLA (Service Level Agreement) profiles as a means to evaluate if the application meets scaling/performance needs.
SLA profiles are defined as a combination of one or more SLAs; in turn, a given individual SLA is based on a metric and some target/reference value.
SLA profiles can be applied at the whole user path level or at individual elements within the user path flow.
From a testing perspective, each time that you apply an SLA to a certain context (e.g. user path, request) you are defining a goal to that context.
This way, at the end of your test session you may evaluate if those goals were met or not (individually and as a whole).
NeoLoad | Xray | Observations/examples |
---|---|---|
(test) scenario | Test (generic/unstructured)
Note: this Test is usually auto-provisioned the first time whenever importing test results and reused afterwards | |
(scenario) test results | Test Run within a Test Execution
| |
SLA's | multiple entries in the Test Run details | |
status of test results | status of the Test Run | based on the status of each SLA |
Please follow the instructions detailed by NeoLoad's team here.
you may link your scenario to existent requirements in Jira and thus see the impact on the coverage calculated for them. You can link it as usual, by creating a "tests" link between the requirement and the Test issue or you can do it automatically whenever importing the results back to Xray. In the later, you need to add the issue key of the requirement as one value in the "Tags" parameter of the "SendXrayContext" action
For specific questions concerning NeoLoad, please use Neotsys support resources.
Please refer to the following resources for more information: