Setting Transaction Thresholds in Jenkins

The Transaction Threshold command—which was made available in the CloudTest Plugin, version 2.17—provides users with the ability to automate the validation of Transactions in a composition using CloudTest metrics, such as Average Response Time or Errors per Transaction. For example, if a threshold of 3000 ms is set on Average Response Time, any result outside that limit will fail the test.

Transaction Thresholds are automatically validated during each Jenkins build and can be set on any non-nested transactions you've placed into your test composition(s).

Note: The Service-Level Agreement feature is an alternative to setting up a Transaction Threshold using the Jenkins Plugin. Please see the Service-Level Agreement help article for more details.
Tip: The CloudTest Jenkins Plugin uses the scommand utility to output the JUnit xml output to display validations on transaction. Any JUnit-ready tool can use this JUnit XML output. For more information, refer to the Knowledge Base article, sCommand Reference (Play command, Validations argument).

Transaction Threshold validation status is posted in the Jenkins build log (shown above) for each threshold that has been set. Using this feature provides a simple means to track regression(s) that are caused by the build actions that changed (whether deployment, code change, etc.). By setting Transaction Thresholds, the plug-in can be made to easily track regressions, or other types of issues caused by this recent change.