This guest blog post is brought to you by Alex Zhitnitsky, Director of Product Marketing at OverOps.
It’s no secret that 100% test code coverage ≠ 100% of critical issues identified. Developers, build engineers, and managers are throwing everything they have at this problem – rigorous code reviews, static analysis, and every possible type of automated test they can think of, but the facts of the matter stay the same – code still breaks.
The reason for this is that testing requires foresight. You can’t predict the future with absolute certainty, and the level of foresight that’s required
Stop Bad Code from Being Promoted in TeamCity Build Chains, with OverOps
by