← ClaudeAtlas

rabbitmq-testslisted

Use whenever RabbitMQ producers or consumers (pika, amqplib, RabbitMQ.Client, spring-amqp) need tests: work queues, pub/sub, routing, topics and RPC, publisher confirms, ack, nack and requeue, durable and quorum queues, with the Testcontainers RabbitMQ image.
testland/qa · ★ 13 · Testing & QA · score 80
Install: claude install-skill testland/qa
# rabbitmq-tests ## Overview RabbitMQ is the leading OSS AMQP message broker. Per [rabbitmq.com/tutorials][rmq-tut], the canonical learning path is six tutorials covering progressively more sophisticated patterns: [rmq-tut]: https://www.rabbitmq.com/tutorials | Tutorial | Pattern | |---|---| | Hello World! | Single producer → single consumer | | Work Queues | Producer → multiple competing consumers (round-robin) | | Publish/Subscribe | Fanout exchange → multiple consumers (broadcast) | | Routing | Direct exchange with routing keys | | Topics | Topic exchange with wildcard routing patterns | | RPC | Request-reply via reply-to + correlation-id | All six tutorials exist in both AMQP 0.9.1 and AMQP 1.0 variants per [rmq-tut][rmq-tut]; AMQP 0.9.1 also has a 7th tutorial - Publisher Confirms - for delivery guarantees. Per [rmq-tut][rmq-tut]: "Executable versions of these tutorials [are open source](https://github.com/rabbitmq/rabbitmq-tutorials)." ## When to use - The repo has RabbitMQ producer / consumer code (pika in Python, amqplib in Node.js, RabbitMQ.Client in .NET, spring-amqp in Java). - The user writes unit tests for the producer/consumer logic. - The user writes integration tests against a real RabbitMQ broker (Docker / Testcontainers). - A test verifies ack semantics, retry-via-requeue, dead-letter exchanges, or publisher confirms. ## Step 1 - Test approach Three approaches: | Approach | Pros | Cons | |---|---|---| | Mock the AMQP client (pika.BlockingCon