What are some disadvantages of code coverage as a measure for how well a system or product is tested? (three answers)

The correct answer is A. It does not measure usability D. It does not ensure that the most important or highest risk areas of the code are being exercised by E. It could create incentives to write tests that simply increase code coverage, rather than tests that. Not being able to explain to management should never be the reason to not do it. It doesn't only provide some data to programmers, the problem is that code coverage alone is not meaning a lot.

Test Driven Development

Question

Options

AIt does not measure usability
BIt is too complicated to explain to management
CIt only provides insights to programmers
DIt does not ensure that the most important or highest risk areas of the code are being exercised by
EIt could create incentives to write tests that simply increase code coverage, rather than tests that

How the community answered

(16 responses)

A
81% (13)
B
6% (1)
C
13% (2)

Explanation

Not being able to explain to management should never be the reason to not do it. It doesn't only provide some data to programmers, the problem is that code coverage alone is not meaning a lot.

Topics

#code coverage#test quality#testing metrics#coverage limitations

Community Discussion

No community discussion yet for this question.

Full PSD Practice