Integration Test Coverage #56
Description
Today, although Peanar has been battle-tested in production by Rechat, making significant changes is always very risky due to the lack of automated tests; there’s always the possibility that we might miss some edge case and break the functionality which is something no one wants.
We need at least >80% of combined unit and integration test coverage before we can continue developing Peanar and expanding its feature-set. The goal for this issue would be to get that level of integration test coverage on each of the following components:
- ChannelPool
- Broker
- Consumer
- Worker
- Job
- Registry
- PeanarApp
Integration testing should be done against a real RabbitMQ instance and should include as many potentially impactful failure scenarios as possible.