All of those tests you have and none of them cover Message Queues
summary
Shows concrete solutions: builds a fake in-memory MQ plus a recorder that waits for acknowledgments to make fast, deterministic tests that catch poison messages, rejections, retries and idempotency; measures that creating a dedicated real queue per test costs about 350ms so uses dedicated queue per test only for dead-letter and retry behaviors; demonstrates contract options with Pact and npm schema packages and explains when a real RabbitMQ SQS or Kafka run is still necessary.
AI-written summary · about
chapters (7)
- 0:00Message queue testing challenges
- 4:04Isolating queue logic risks
- 11:09End-to-end testing failures
- 16:54Fake message queues for testing
- 21:04Message schema contract problems
- 33:49Contract testing strategy
- 34:31Q&A on Pact and versioning
related talks
46mReal-world Examples of Message Queue Usage: Insights from RabbitMQ
01h 03mChoosing the Right Messaging Solution for Your Architecture
38mTake The Path Of Least Resistance For Your Test Data
50mMiddleware Showdown: Exploring Diverse Messaging Solutions
39mReal World RabbitMQ: Exploring Practical Applications
42mIt's like 10,000 streams when what you need is a queue
41mForget about HTTP
39mMastering message Queues