Unity of Code Coverage
How do we release a product that meets client expectations, while reducing the time taken to deliver that product? Quality engineers face great challenges: first deciding how much testing is enough before releasing a new feature and second deciding how many testing resources are needed.
Step forward the tools that can help us! These are tools like Sonar and JaCoCo.
Sonar is used to monitor and review the code health and more particularly code coverage. JaCoCo is a tool for Java Code Coverage measurement. The feature that makes Jacoco a good choice when evaluating code coverage tools is its ability to instrument Binaries. With this tool you can measure code coverage for Unit Tests, code coverage of UI testing of the application and all testing activities post-build like manual testing.
In this presentation we will explain how JaCoCo and Sonar allow us to incorporate code coverage of integration tests to the set of metrics we manage under continuous integration/continuous quality assurance.
Awareness of both integration and unit test coverage provides the development team and product owners with a more accurate picture of test completeness. This more complete picture can be used to justify reducing testing in certain areas, while identifying more risky portions of the code that are not tested in a production-like environment. It also shows trends in the quality/completeness of integration tests that were not previously measurable.