Запуск jmeter из командной строки windows

Для запуска JMeter из командной строки необходимо сначала убедиться, что Java установлена на вашем компьютере. Затем следуйте этим шагам:

Скачайте JMeter с официального сайта Apache JMeter (https://jmeter.apache.org/download_jmeter.cgi) и распакуйте архив.
Откройте командную строку на вашем компьютере.
Перейдите в папку с распакованным JMeter.
Для запуска JMeter из командной строки используйте команду:

jmeter.sh

для Linux или MacOS

jmeter.bat

для Windows

После запуска JMeter из командной строки вы увидите GUI интерфейс JMeter, где вы сможете создавать и запускать тестовые планы.

Дополнительно, JMeter также поддерживает non-GUI режим, который позволяет запускать тесты без интерфейса. Для запуска JMeter в non-GUI режиме используйте команду:

jmeter -n -t [путь к тестовому плану] -l [путь к файлу результатов тестирования]

где -n указывает на non-GUI режим, -t [путь к тестовому плану] указывает на путь к вашему тестовому плану, а -l [путь к файлу результатов тестирования] указывает на путь к файлу, куда будут записаны результаты тестирования.

Источник

To run a JMeter test from the command line, we need to follow the steps below:

Open a terminal or command prompt.
Navigate to the directory where the JMeter executable file is located.
- In our case, the file is inside the JMeter’s bin directory /opt/jmeter/bin. If we have added the directory that contains the jmeter command to our system’s PATH environment variable, we can run the jmeter command from any directory.
  
  Note: To find the full path of our saved file in the current directory and its subdirectories, we can use the find command in the following manner: find . -name "test.jmx" where test.jmx is the name of our executable file.

Enter the following command to run the test:

jmeter -n -t /path/to/your/test.jmx -l /path/to/save/results.csv

Let’s take a look at how we can do this.

Run the `test.jmx` file

To add the directory (/opt/jmeter/bin) to the PATH environment variable permanently (not just for the current session) from the terminal, enter the following command:

echo 'export PATH="$PATH:/opt/jmeter/bin"' >> ~/.bashrc
source ~/.bashrc

Line 1: The echo command appends the export PATH="PATH:/opt/jmeter/bin"' >> ~/.bashrc line to the end of the .bashrc file[object Object] in the user’s home directory (~ refers to the user’s home directory). This sets the PATH variable for the current user and allows the jmeter command to be executed from anywhere in the terminal.
Line 2: The source ~/.bashrc reloads the .bashrc file in the current shell session so that the updated PATH variable is available for the current session.

To gain hands-on experience, please run the above commands in the following terminal to add the bin directory to the PATH environment variable.

If we want to run the test.jmx file and place the test results in the result.csv file that we have already created in the JMeter’s bin folder, we enter the following commands:

# command to run the JMeter test

jmeter -n -t ./opt/jmeter/bin/test.jmx -l result.csv

# command to display the contents of the CSV file (result.csv) in a human-readable format

csvtool readable result.csv

In the code above:

-n specifies JMeter to run the test in a non-GUI (CLI) mode
-t specifies the path to the JMeter test file (.jmx)
-l specifies the path to save the test results file
csvtool displays the .csv file in the terminal in a human-readable format with headers for each column

We have included the commands above in the terminal below. Click the terminal to see the tests being executed.

Источник

Updated February 21, 2023

Introduction to JMeter Command Line

JMeter is an open-source tool used to perform load and performance testing on the application. There are two ways to use JMeter: the graphical user interface and command line mode. JMeter provides different functionality when we use command line mode, such as we can generate the CSV or say that the XML file consists of the output of test execution. In other words, we can say that it stores the result of the HTML report. Normally JMeter, by default, provides the summary of load testing after the execution as well as we can also see the real-time output of test execution as per our requirements.

What is the JMeter Command-Line?

Apache JMeter is an open-source testing application. JMeter capacities to examine and gauge the presentation of web applications with an assortment of different administrations. In addition, the GUI method of JMeter is ideal for adding and altering new arrangement components, string gatherings, and samplers, which allows you to see various audience members helping with troubleshooting.

Nonetheless, the GUI mode has a constraint that dials back the CPU while running the recorded content. Assuming we are running different audience members in content, it influences the JMeter execution. The content should be run in non-GUI mode to defeat such a circumstance. There is an advantage to driving more demands each second out of JMeter in non-GUI mode.

A command-line interface (CLI) processes orders to a PC program as lines of text. The program that handles the connection point is an order line translator or order line processor.

Working frameworks execute an order line interface in a shell for intelligent admittance to working framework capacities or administrations.

We will execute the JMeter Tests in Non-GUI mode. However, before that, we want to comprehend why we want to execute the Test In Non-GUI mode.

Typically when we execute the Request in the Non-GUI Mode, it will send a few solicitations to the server and get the reaction, and again it will require some investment to produce the reports and view the outcomes to the client. So it will interact with the UI of some sort or another Level.

So we cannot get the Actual outcome when we send the solicitation and help a reaction through UI. So we run the JMeter Test in order briefly to keep away from that circumstance.

Now let’s see why we need to use command line mode.

Expanding strings (after a specific limit) because of which JMeter crashes in the GUI mode.
For serious test situations (ex: shopping application: login-view item put on truck view tab eliminate item take care of bill), JMeter consumes memory and CPU, which might influence your experimental outcomes.
To build JMeter capacities, for example, to get more demands each second.

How to Run JMeter Command-Line?

Now let’s see how we can run JMeter on command line mode.

First, we need to open the command line prompt window, as shown in the following screenshot.

In the second step, we need to go into the bin folder of JMeter. After that, we need to enter the command,

JMeter -n –t test.jmx -l testresults.jtl

We need to set the different parameters in the above command as follows.

n is used to specify the JMeter run test into a non-GUI mode that is command line mode.
t Is used to specify the name of the JMX file that contains the plan of a test, and it depends on the user.
l It is used to specify the name of the JMeter text log file and consists of the log result.
j It is used to specify the name of JMeter log files.

After executing the above command, we see the generated result in the specified location in CSV format; here, we can add any listener as per our requirement, but we need to open JMeter into a GUI mode for that purpose.

JMeter Command Line Configuration

Now let’s see how we can configure the command line mode of JMeter as follows.

In the above point, we already discussed how to run the JMeter command line mode, but if we want to run JMeter for distributed testing, we need to do some settings on our local machine.

First, we need to ensure we installed the updated version of JMeter.
After that, we need to make some changes to the JMeter properties file for IPs and slaves; in this step, we also ensure the master and slave are located on the same subnet.
Now we need to execute the JMeter server on every slave, so for that purpose, we need to execute the bat file of JMeter from the bin folder.
Report generation and reaming all things are the same.

Example of JMeter Command Line

Now let’s see the example for better understanding as follows.

First, we need to add the test plan into the JMeter, as shown in the following screenshot.

We need to add the listener to view the output, as shown in the following screenshot.

Now save the test plan, minimize the current window and execute the below-mentioned command.

JMeter -n -t D:\Software\apache-JMeter-5.4.1\apache-JMeter-5.4.1\bin\ View Results Tree.jmx -l D:\Software\apache-JMeter-5.4.1\apache-JMeter-5.4.1\bin\result.csv

Explanation

In the above command, we specify all parameters such as the name of the test plan, location of the test plan, where we need to store the result of the test plan, etc. Then, we can make the changes in the above command as per our requirements. We illustrated the final output of the above command by using the following screenshot.

After executing the above command, the CSV file generated, as shown below, is as follows.

Now we need to open that file to see the output of the test plan, as shown in the following screenshot.

Conclusion

We hope from this article you learn more about the JMeter command line. From the above article, we have taken in the essential idea of the JMeter command line and see the representation and example of the JMeter command line. Furthermore, this article taught us how and when to use the JMeter command line.

For Web Development Services,

Источник

A command-line interface (CLI) processes commands to a computer program in the form of lines of text. The program which handles the interface is called a command-line interpreter or command-line processor.

Operating systems implement a command-line interface in a shell for interactive access to operating system functions or services.

We are going to execute the JMeter Tests in Non-GUI mode. Before that, we need to understand why we need to Execute the Test In Non-GUI mode.

Normally when we execute the Request in the Non-GUI Mode, it will send some requests to the server and get the response, and again it will take some time to generate the reports and view in the results to the user. so it will do some kind of process in the UI Level.

So we can not get the Actual result when we send the request and getting a response through UI. To avoid that situation we run JMeter Test in command prompt.

Basically GUI consumes more Memory/Resources.
And, GUI not recommended for heavy load testing because we will not get accurate results.
When we run the JMeter through the command line it can also be integrated with other systems-Jenkins and other continuo s integration tools.

The following example demonstrates how to run the JMeter in the Command-Line.

Open the JMeter in your system and then add Thread Group and then Three HTTP Request to the Thread Group.
And enter the Number of Threads as 5 and the Ramp-up period as 2 and then, the Loop count as 3.

Картинка с сайта: chercher.tech
Rename the HTTP Requests as HTTP Request1, HTTP Request2 and HTTP Request3.

Картинка с сайта: chercher.tech
In the HTTP Request1 add blazedemo link in the server and enter the path as /Register

Картинка с сайта: chercher.tech
Enter the login details in the Second request as below.

Картинка с сайта: chercher.tech
Enter the root page details in the third request as below.

Картинка с сайта: chercher.tech
Next, add View Result Tree Listener into the Thread Group to see the report.

Картинка с сайта: chercher.tech
Enter the Result.csv file path in the view result tree as shown below.
Before running the test plan through the command line make sure that the CSV file is not available at the file location. So I am deleting the result.csv file from the MyPlans folder.
We are going to execute the command which not only going to create the CSV file, by using the details of the CSV file we also going to create an HTML report.
We can create an HTML report in two approaches:
- To Create an HTML report at the end of the Test : which means, at the time of running the HTTP request we can create the HTML file.
  The Command to create CSV file and HTML report at once is as follow
```
jmeter -n -t "D:Jmeter_Projectapache-jmeter-5.2.1inMyPlanscommandline.jmx" -l "D:Jmeter_Projectapache-jmeter-5.2.1inMyPlans
esult.csv" -e -o "D:Jmeter_Projectapache-jmeter-5.2.1inMyPlanshtmlReports"
```
- Creating an HTML report with standalone CSV file : In this case, we have a CSV file, by using the details of this CSV file we can create the HTML report.
  The Command to create CSV file and HTML report is as follow
```
jmeter -g "D:Jmeter_Projectapache-jmeter-5.2.1inMyPlans
esult.csv" -o ""D:Jmeter_Projectapache-jmeter-5.2.1inMyPlanshtmlReports"
```
Open the Command prompt in the Bin folder of JMeter and then execute the first command as shown below.

Картинка с сайта: chercher.tech

Картинка с сайта: chercher.tech
After executing the command in the command prompt, if you open your file location you will find both Result.csv file and then HTML Report.

Картинка с сайта: chercher.tech
Now I am going to delete the HTML Report and I have only Result.csv file.

Картинка с сайта: chercher.tech
Click on the HTML Report you fille below files inside the folder.

Картинка с сайта: chercher.tech
Click on the Index file you will see the Dashboard, Customer Graphs, and Charts.

Картинка с сайта: chercher.tech
By using the Result.csv file details I am going to create an HTML report, but this time the Command will be changing a little bit as below.
In the folder, you can see that the HTML report has been created.

Картинка с сайта: chercher.tech