It provides a measurable value to stakeholders on software quality.However, it is possible to achieve high percentages (“for the sake of coverage”) without improving maintainability. High percentages can imply code that is more maintainable and readable.Software with high results is less likely to contain undetected bugs stemming from coding errors, non-adherence to good coding practices, or overly complex code.Test coverage is a measurement of the degree to which a test or testing suite actually checks the full extent of a program’s functionality. Many use the terms “code coverage” and “test coverage” interchangeably. Optimizing Test Automation | Download White Paper > Tools that measure code coverage normally express this metric as a percentage.
This measures the number of lines of source code executed during a given test suite for a program. In this article, we’ll explain the inner workings of this popular testing metric and reveal that while this metric often goes together with great quality software, it does not provide a complete picture of quality, which can sometimes lead to incorrect decisions or poor testing practice. How does code coverage work, and is it really important to measure it?
0 kommentar(er)
