JMeter Learning -023-jmeter Command Line (non-GUI) mode detail (i)

This article describes the JMeter distributed run scripts to better achieve pre-set performance testing (concurrency) scenarios. At the same time, the JMeter command line (non-GUI) mode is also mentioned in the first section of the previous article, so this article continues with the previous article for a detailed explanation of JMeter's command-line mode.

First, the application scenario

1. No interactive interface or environmental restrictions (Linux text model)

2. Remote or distributed execution

3, continuous integration, through Shell script or batch command can be executed, generated test results can be directly used by the report generation module, easy to generate reports

Ii. Advantages of the command line mode

1. Save system resources: No need to start the interface, save system resources

2, convenient and fast: only need to start the command line, enter the command can be executed, is for the command of the most loved

3. Easy Continuous Integration: can be executed through shell script commands

Three, detailed parameters

Iv. demonstration of examples

1. Execute test Script

Jmeter-n-T JMeter Distributed test example. jmx

The command-line window output looks like this:

The log default output path is the same as the Jmx script path.

2. Specify the result file and log path

Jmeter-n-T JMeter Distributed test example. jmx-l report\01-result.csv-j Report\01-log.log

The command-line window output looks like this:

If the log path does not exist, JMeter is not created automatically, and the log is output to the command-line window.

The resulting file type is JTL or csv, and you can view the final results by browsing the results file through the JMeter aggregation report, as follows:

3. Distributed (remote) execution of default server list

Jmeter-n-T JMeter Distributed test example. jmx-r-L REPORT\01-RESULT.CSV-J Report\01-log.log

The command-line window output looks like this:

The execution machine command line output looks like this:

the log files on the execution machine (Slave) side are generated by default in the user directory.

If the situation appears as shown, please check whether the network is unblocked, the server domain name (IP) and port is correct, the actuator is started jmeter-server.bat or jmeter-server

4. Distributed (remote) Execution server list

Jmeter-n-T JMeter Distributed test example. jmx-r 10.9.215.47:1029-l report\01-result.csv-j Report\01-log.log

The command-line window output looks like this:

At this point, This article successfully concluded, I hope this article can give beginners JMeter you a reference.

Finally, very grateful to the pro-stop, I hope this article can be pro helpful. Warmly welcome the kiss to discuss together and progress together. Thank you so much! ^_^

Save

Save

Save

Save

JMeter Learning -023-jmeter Command Line (non-GUI) mode detail (i)