Why you should think about Code Coverage

Can you guarantee your smoke test suite, your regression test suite cover all the functionalities of the application you are testing?

How would you do a quantitative analysis to evaluate the number of tests vs different application functionalities?

How would you show case that you test the application under test, well enough to your management?

The answer is a code coverage test. One of the oldest non-functional test type used in the industry. Code coverage test will explain you the percentage of the execution paths that have traversed through during the functional test.

A high percentage of test coverage in a code coverage test would give the QA engineers more confidence on the test suites they have and reduces the defect leakage. On the other hand, less coverage would give a good actionable report for both QA engineers and developers.

• To add more tests for missing areas to increase the coverage.
• To remove the obsolete code from the repository.

How often do you think you should be doing a code coverage test?

Ideally well before the release, if there are new features, once all the features have been merged and deployed to the testing environment in a stable build, where your regression tests…