Our Test Gap analysis and Test Impact analysis automatically monitor the execution of your application to determine which code is covered in tests.
As a result, they are objective with respect to what has been tested and, more importantly, what hasn’t. No personal judgement or gut feeling involved.
However, when we first setup the analyses with our customers, we often find that the measurements differ (significantly!) from their expectations. Often, this is because other coverage tools report different coverage numbers.
This post explores causes for such differences.