The purpose of the check mojo is to validate the result of executing Your performancetest to see whether performance goals have been met.
It is possible to validate responsetimes, throughput and garbage collection statistics. It is also possible to halt the build, if any of the requests fail (eg a JUnit testcase failing or an Http request resulting in an http error code).
For details on the possible parameters, see chronos:check
The goal is typically invoked by attaching it as an execution. The will cause validations to be performed in the verify phase of the build lifecycle.
Example:
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>chronos-maven-plugin</artifactId>
<configuration>
<input>${basedir}/src/main/resources/simplewebplan.jmx</input>
<responsetimeaverage>550.0</responsetimeaverage>
<maxthroughput>3.2</maxthroughput>
</configuration>
<executions>
<execution>
<goals>
<goal>jmeter</goal>
<goal>check</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>