Skip to content

Latest commit

 

History

History
37 lines (26 loc) · 2.26 KB

testharness.md

File metadata and controls

37 lines (26 loc) · 2.26 KB
Raw

Test Harnesses

We use a number of different test harnesses and tools in our testing of MQ. Many of which have been made publicly available via open-source.

There are two different messaging test applications:

  • CPH
    C Based Test Harness utilising the MQI API
  • JMSTestHarness
    JMS Based Test Harness

These have been containerized into simple to run tools:

  • cphtestp
    Containerized version of CPH
  • jmstestp
    Containerized version of JMSTestHarness

These repositories contain Dockerfiles and instructions to help you create the required Docker images, you need to provide MQ (the freely available Developer Edition is fine) and accept the license conditions. Its because of these restrictions that we cannot make the built images publicly available.

JMeter

JMeter can also be used with MQ (though we recommend CPH or JMSTestHarness above). If you intend to use JMeter, it's important to configure it correctly as some existing guidance on use with MQ is not optimal. Each thread connecting to MQ should have it's own session, for instance. We have provided a sample JMeter script with instructions here, to get you started developing your own.

IO Testing

There is also a tool for testing your IO performance (in the manner in which MQ writes) called MQLDT (MQ Log Disk Tester).

This also now has a containerized version available here mqldt-c and the automatically built image is available from quay.io at quay.io/stmassey/mqldt. This image can be easily obtained by:

podman pull quay.io/stmassey/mqldt

Network testing

iperf3 is the latest incarnation of the popular network testing tool and we use it frequently to check network performance between servers. A containerized version has been made available which can be used in both local docker/podman runtimes and also in Kubernetes/OpenShift environments: