> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/automation/desktop-client/jmeter.md).
# JMeter
Integrate JMeter with aqua’s desktop client for automated testing. Edit scripts, map variables, view real-time load results, and configure agents for seamless performance test execution.
First, you go into a test case and click on Automation. Here, you can add a JMeter script.
{% hint style="info" %}
The version number of the JMeter agent must match the version number of JMeter. Take a look at system requirements to look for supported versions.
{% endhint %}
A test script template is now created and can be edited with the external editor JMeter. You have the option to record a test case with JMeter.
To run an automated test, the test case must be executed in the same way as the manual tests. Open the test case and click on the Run button. If this is an automated test and if agents are available in the network, then a selection of possible test systems will be displayed.
A new window provides the load test results in real-time in the form of diagrams. The diagrams are not available immediately but after 30 seconds when the first measurement results of the agents have been evaluated, the tab will appear.
Variables from the aqua test case are also automatically transferred to the JMeter script. This means that you can define variables such as "user name", "password" or "URL" in the variable manager and then execute the JMeter test case with the desired values in the variables when selecting the value sets. In the JMeter script, the variables can then be used like normal variables, i.e. via **${variable name}**. The variable name must exactly match the variable name in aqua (e.g. username or password or URL).
## Configure agent
##
To configure the agent open agent.properties.
Here, you have to specify the Agent Code and the aquaService URL as follows:
agentCode=**pvq6wrb70huknv47ji39**a
ggregateSeconds=20
aquaServiceUrl=[**http://youraquaserver/aquaAPI/aquaagentwebservice.asmx**](http://youraquaserver/aquaAPI/aquaagentwebservice.asmx)
keepAliveSendingFrequency=30
resultsDirectory=results
tempDirectory=temp
sendSUTErrors=true
proxyHost=
proxyPort=
proxyUsername=
proxyPassword=
{% hint style="info" %}
If you use plugins in your JMeter scripts, these plugins must also be stored in the lib/ext folder in the agent folder.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.aqua-cloud.io/documentation/automation/desktop-client/jmeter.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
