Continuous Integration with JMeter

Continuous Integration, or CI as it is often referred to, is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early. This practice has been around since the late 90s, and more and more companies have embraced it so much that it has now become 'the de facto practice'.

As such, it would be advantageous and beneficial to have JMeter fit into this pipeline somehow. Wouldn't it be great to have performance tests automatically run on every code check-in to version control system (VCS) to know when an introduced change increased or decreased the application's performance? Such insights become indispensible as the application grows in complexity and help alleviate changes that will adversely impact the system from being introduced.

How to do it…

In this recipe, we will cover how to integrate JMeter into a continuous...