wtf is rabbitmq-jms-cts?

This project, rabbitmq-jms-cts, is a verification tool that checks whether a piece of software built by the RabbitMQ team correctly follows an industry standard called JMS (Java Message Service). JMS is a standard way for Java applications to send messages to each other, like passing notes between different parts of a system. Because RabbitMQ is a messaging platform that uses its own communication methods, the team created a separate "client" program to translate between RabbitMQ and the JMS standard. This test suite exists to prove that the translation works flawlessly and meets all the official rules. The suite works by running a series of standardized tests against the RabbitMQ JMS client. These tests are based on an existing, official testing framework designed specifically to verify JMS compliance. To run the tests, you need a running RabbitMQ server with a specific plugin turned on. Once everything is set up, a developer runs a simple command that triggers the test suite to send various types of messages and verify that the RabbitMQ client handles them exactly as the JMS standard dictates. After the tests finish, the tool generates HTML reports showing how well the client performed. The primary audience for this repository is the engineering team maintaining the RabbitMQ JMS client, or contributors who want to verify their changes don't break standard compatibility. For example, if a developer updates how the RabbitMQ client handles message routing or acknowledgments, they would run this test suite to ensure the update still complies with the strict rules that Java applications expect. The project does not have much of a purpose outside of this specific quality assurance workflow. Notably, the project offers two ways to run the tests: against an existing RabbitMQ server you already have running, or by letting the test process automatically start and stop a temporary server for you. Beyond that, the README doesn't go into detail about the inner workings of the tests or any deeper architectural choices, as it is a straightforward utility built to serve a specific verification need.