Doing performance testing typically runs JMeter in the command-line mode of the None GUI. For example:
Jmeter-n-t/opt/las/jmeter/testplan/test.jmx-l/OPT/LAS/JMETER/TESTREPORT/TEST.JTL
The contents of the JTL can be modified by modifying the Jmeter.properties settings in the JMeter bin directory, for example:
Jmeter.save.saveservice.response_code=true
Jmeter.save.saveservice.response_data.on_error=true
There are several ways to visualize the resulting JTL results:
1> opens directly inside the JMeter GUI
Create a new listener, such as viewing the results tree, and then selecting the Jtl file in the file name browse under "All data written to a file" to show
2> Open in Excel
Several XSL style templates are available in JMeter's extra directory, such as jmeter-results-report.xsl, jmeter-results-report_21.xsl, etc.
Open the Jtl file and insert a line of style between <?xml version= "1.0" encoding= "UTF-8"?> and <testresults version= "1.2" >, for example:
<?xml-stylesheet type= "text/xsl" href= "D:\JMeter\extras\jmeter-results-report_21.xsl"?>
Then drag JTL into Excel to
3> Open in HTML
Run command xsltproc/opt/las/jmeter/jmeter/extras/jmeter-results-report_21.xsl test.jtl > test.html
This is just a summary report.
Http://www.shanhe.me/2011/06/07/new-xsl-stylesheet-for-jmeter-command-line-results-report This article provides a jmeter.results.shanhe.me.xsl that can be seen in detail.
Can be downloaded from http://download.csdn.NET/detail/sundongsdu/5623225
5> Jenkins Integration.
Installing performance Plugin and HTML Publisher Plugin in Jenkins, how to install see http://blog.csdn.Net/sundongsdu/article/details/8276787
After installation, first add the shell command to execute the Jemter in the build step, for example
/opt/las/jmeter/jmeter/bin/jmeter-n-t/opt/las/jmeter/testplan/wifipush.jmx-l/opt/las/JMeter/TestReport/ Test.jtl
And then add a shell build to build the HTML
XSLTPROC/OPT/LAS/JMETER/JMETER/EXTRAS/JMETER.RESULTS.SHANHE.ME.XSL/OPT/LAS/JMETER/TESTREPORT/TEST.JTL >/opt/ Las/jmeter/testreport/test.html
Of course, in the first step of the build you can run a shell to delete the existing JTL and HTML files so that the latest data is used in the post-build steps.
Add the Publish Performance test result report and the publish HTML reports in the job post-build operation, configured as follows:
JMeter Test Report Visualization (Excel, HTML, and Jenkins integration)