Tested versions¶
| Thing | Version | Where it is recorded |
|---|---|---|
| Broker image the suite runs against | rabbitmq:4.3.5-management |
image in test/integration/main_test.go |
| Broker behaviour recorded in the code | 4.3.5 | comments in session.go (measured 2026-09-05 and 2026-09-07) |
| Core it implements | go/messaging v0.9.0 | go.mod |
| AMQP client | rabbitmq/amqp091-go v1.16.0 |
go.mod |
| Container harness | testcontainers-go v0.44.0 and its modules/rabbitmq |
go.mod |
| go/envelope | v0.1.0 | go.mod |
| go/envelope-cloudevents | v0.1.0 | go.mod |
| go/envelope-masstransit | v0.1.0 | go.mod |
| go/envelope-nservicebus | v0.1.0 | go.mod |
| Go | 1.27.3 | go directive in go.mod |
The suite starts the 4.3.5-management image through testcontainers-go, which includes the
management plugin. The unit tests need no broker. The integration tests need a Docker daemon and run
only with INT_TEST_INTEGRATION=1; see
Run the conformance suite.
What "tested" covers¶
- RabbitMQ 4.3.5 only. No other 4.x, and no 3.x, is run, although the doc comment on
Newdescribes one constructor for both. - Quorum queues for
AtLeastOnce. The suite'sAtMostOncequeues are declared with no arguments, and the refusal of a classic queue is checked by its own test. - A single node. The suite restarts the one container; no cluster, failover or network partition is run. The link-death row deletes the queue, which makes the broker cancel the consumer.
- Plain AMQP, not
amqps://, and the defaultguestaccount.
Observed on 4.3.5 while writing these pages¶
A quorum queue created with no x-delivery-limit reports a delivery_limit of 20 through the
management API, and a queue created with x-delivery-limit: 4 reports 4. Both appeared after the
API's statistics interval, not at once. This is a measurement of one broker, not something the
adapter's suite asserts.