The Rapid Increase in Bug Count: An explanation

[iancooper]

If you're watching the repo and seeing the bug count climb, you may be wondering what is happening. The answer is that two PRs are throwing up bugs as side issues as they push towards their goal:

• Generated MessagingGateway conformance tests: As we move to a standardized test suite and post the pass at making our reject/requeue/delay support universal, bugs are showing up where some providers fail to implement the whole suite correctly. The work to create a universal feature set precedes the landing of the generated test suite, and adding universal behaviors to that suite has exposed coverage gaps and bugs. This is a good thing, and a benefit of the universal suite driving quality to ensure all of our MessagingGateways are high quality.
• Improved docs. As we improve the docs, we write samples, and the samples sometimes surface anomalies, often related to accumulated version differences. Every big docs rewrite we do tends to turn up a few. Again, that is a good thing; it flushes out errors.

So this is positive, as long as we can address those bugs.

The good news is that the \bugfix flow works well and can work through these individual problems, so once we have them all, we should be able to pick them up and improve quality quickly.

A key question might be why this bugs are there though, and that is a larger one, that suggests we need to pay more attention to tools like code coverage and mutation testing, so we can come back to those