This sub-repository aims to describe the setup required for using JMeter on OpenShift, from the creation of a JMeter image to its use for running test plans in non-GUI mode.
|
|
TODO: To add test results dashboard and analysis |
The recommended approach is to use JMeter GUI for designing your test plan. You may have installed it on your machine or you may run it on OpenShift, although this part has not yet been covered here. Running the test plan should however be done in non-GUI mode for better performance. OpenShift is best suited for this step.
Using JMeter GUI for the design phase provides a quick feedback loop. The test plan can then be tweaked till it is deemed ready and can be added to the continuous integration pipeline.
Although the test plan can be manually run on OpenShift the idea is to get that automated by a tool for continuous integration. This will enable running non-regression tests that also cover performance aspects every time a new version is pushed to the central repository or nightly if resources are constrained during the day. We have used Jenkins for demonstrating how it can be done.
See: Jenkins
See the following chapters for details: