有两个插件能够实现在Maven build集成Jmeter测试， jmeter-maven-plugin 和 chronos-maven-plugin. 选择哪一个取决于情况，下面是一些判断标准：
- 该插件不应该依赖于本地JMeter的安装。
- 它必须能够从命令行启动JMeter测试（无GUI）。
- JMeter的图形用户界面也应该通过插件（例如，通过一个单独的Maven目标）直接实现。
- 它包含JMeter的插件。
- 该插件应该产生有意义的报告。
第一第二条两个都满足，jmeter-maven-plugin可以在无图形情况下使用一个简单的附加依赖项kg.apc:jmeter-plugins直接使用使用JMeter，这点是 jmeter-chronos-maven-plugin没有的。
下面是一段来自 jmeter-maven-example的配置：
<plugin>
<groupId>com.lazerycode.jmeter</groupId>
<artifactId>jmeter-maven-plugin</artifactId>
<version>1.8.1</version>
<configuration>
<!--
By default the test results are saved in a file
/target/jmeter/results/<testname>-<timestamp>.jtl
Further processing is easier without timestamp though.
-->
<testResultsTimestamp>false</testResultsTimestamp>
<!--
To simplify debugging, it is advisable to adapt the loglevel.
The jmeter logs are written to the file jmeter.log.
-->
<overrideRootLogLevel>DEBUG</overrideRootLogLevel>
<!--
By default, the console output during a jmeter test run is suppressed.
We want to display the progress using the listener "Generate Summary Results"
(which periodically prints stats to stdout). Therefore we have to make sure,
that the jmeter output is not suppressed.
-->
<suppressJMeterOutput>false</suppressJMeterOutput>
<!--
If tests fail (e.g. a http-request running into a timeout), the corresponding maven
goal also fails (and subsequent goals aren't executed anymore). We want to create graphs
from test-results, no matter if some requests failed or not, so we ignore jmeter failures.
-->
<ignoreResultFailures>true</ignoreResultFailures>
</configuration>
<dependencies>
<dependency>
<groupId>kg.apc</groupId>
<artifactId>jmeter-plugins</artifactId>
<version>1.0.0</version>
<exclusions>
<!--
Unfortunately some transitive dependencies cannot be found on mvncentral
and we have to explicitly exclude them.
For a complete list, see https://github.com/mlex/jmeter-maven-example/
-->
<exclusion>
<groupId>kg.apc</groupId>
<artifactId>perfmon</artifactId>
</exclusion>
<!-- ... -->
<!--
Because of a bug in the jmeter-maven-plugin (see
https://github.com/Ronnie76er/jmeter-maven-plugin/issues/77) we have to
exclude jmeter dependencies here, too.
-->
<exclusion>
<groupId>org.apache.jmeter</groupId>
<artifactId>jorphan</artifactId>
</exclusion>
<!-- ... -->
</exclusions>
</dependency>
</dependencies>
</plugin>
这个测试文件必须放在 /src/test/jmeter，您可以编辑和执行测试。
测试环境可以是各种，这里结合 Jenkins中创建一个Job，允
许一次点击就可以执行JMeter的测试，首先要使用Maven的属性和配置文件。下面示例项目中定义了两种不同的Maven配置文件，一个用于本地执
行，一个用于从jenkins执行。 Maven的特性是通过userProperties选项传递到JMeter的。
<profiles>
<profile>
<id>local</id>
<properties>
<performancetest.webservice.host>localhost</performancetest.webservice.host>
<performancetest.webservice.port>8080</performancetest.webservice.port>
</properties>
</profile>
<profile>
<id>jenkins</id>
<properties>
<performancetest.webservice.host>my.test.system</performancetest.webservice.host>
<performancetest.webservice.port>80</performancetest.webservice.port>
</properties>
</profile>
<build>
<plugins>
<plugin>
<groupId>com.lazerycode.jmeter</groupId>
<artifactId>jmeter-maven-plugin</artifactId>
<version>1.8.1</version>
<configuration>
<propertiesUser>
<webservice.host>${performancetest.webservice.host}</webservice.host>
<webservice.port>${performancetest.webservice.port}</webservice.port>
</propertiesUser>
</configuration>
</plugin>
</plugins>
</build>
</plugin>
使用Jenkins-CI进行JMeter tests
现在，我们已经为各种环境下制作了不同的Maven配置文件，一个合适的jenkins作业的配置仅仅需要一小步。参数化的构建版
本是jenkins的另一个不错的功能，针对JMeter的测试非常有用。参数可用于例如，允许用户定义负载测试的大小（即：线程数和迭代的次数）。
报表
使用jmeter-graph-maven-plugin集合Jmeter的CMDRunner工具，可以让我们在Maven Build中输出图形结果。
https://github.com/codecentric/jmeter-graph-maven-plugin