From within the description field of the Test Execution issue, you have a link to the test results in NeoLoad Web where you can see finer details.

Test Plan (if you decide to report it against an existing Test Plan).

Define the runtime parameters for your scenario (e.g.

Note: It is also possible to override the auto-provision behavior and enforce results to be reported against an existing Test issue that would need be created beforehand in this case, the Test issue key has to be specified as one of values in the 'Tags' parameter of the SendXra圜ontent action.

Whenever importing the results, a Test issue will usually be auto-provisioned in Xray the name of the scenario will be mapped to the Test' summary and will be used as the unique identifier for the Test (as seen on its Definition field) so it can be reused on subsequent result imports.use a specific, dummy population assigned to the previously created user path.configure the Xray integration parameters.use a specific, dummy user path for configuration the integration with Xray by including the 'SendXra圜ontext' action in the 'Actions' section.Please follow the instructions detailed by NeoLoad's team here. This way, at the end of your test session you may evaluate if those goals were met or not (individually and as a whole). user path, request) you are defining a goal to that context. SLA profiles can be applied at the whole user path level or at individual elements within the user path flow.įrom a testing perspective, each time that you apply an SLA to a certain context (e.g. 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. Optionally, users can define one or more SLA (Service Level Agreement) profiles as a means to evaluate if the application meets scaling/performance needs. duration, load policy, VUs).Ī user path corresponds to the definition of a browsing sequence in the target application it contains, for example, the HTTP requests to be performed. flows) to be exercised along with the running conditions (e.g. Each scenario has a set of user paths (i.e. In NeoLoad, all happens in the context of a working project, which may be created/modified using NeoLoad GUI.Ī project contains one or more (test) scenarios. link results back to an existing Test Plan in Xray.

add labels to Test entity that is used to abstract the scenario.link scenario to an existing 'requirement' in Jira/Xray.identify the project, its version and the revision of the SUTl.automatic provisioning of the test scenario.link to NeoLoad web, for more in-depth results about the testing session.chart with an overview of the testing session.integration with both Xray on Jira server/DC or cloud.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. from within NeoLoad GUI or NeoLoad web) or from a CI/CD pipeline. Performance tests can be triggered manually (e.g. Users may define SLA's based on performance metrics, giving them insights about performance that can be crucial for business. NeoLoad is an enterprise tool for performance and load testing, covering both API and end-to-end application testing.īesides support for web-based applications, it also supports a broader set of applications and protocols, including SAP, Oracle Forms, Adobe Flex, etc.

Neoload documentation