testing and code coverage
Posted May 31, 2006 14:21 UTC (Wed) by jreiser
In reply to: Re: detecting all possible deadlock conditions
Parent article: The kernel lock validator
Put differently: it's not bad idea to run through every possible branch of code at least once anyway ;-) If some code is never triggered in practice, why is the code there and how was it tested to begin with?
First, probably it never has been tested systemmatically; this problem is endemic to the Linux development process. Second, the problem is not only "branches of code [coverage of basic blocks]." The problem is conditional execution paths through multiple basic blocks, including re-convergent fanout (correlated conditions) and partial correctness with "don't care" conditions.
to post comments)