Statement coverage is commonly used as a measure of test suite quality. Coverage is often
used as a part of a code review process: if a patch decreases overall coverage, or is itself …

The coverage of a test suite is often used as a proxy for its ability to detect faults. However,
previous studies that investigated the correlation between code coverage and test suite …

Code coverage is a measure of the degree to which a test suite exercises a software system.
Although coverage is well established in software engineering research, deployment in …

Test suite reduction seeks to reduce the number of test cases in a test suite while retaining a
high percentage of the original suite's fault detection effectiveness. Most approaches to this …

Not all bugs lead to program crashes, and not always is there a formal specification to check
the correctness of a software test's outcome. A common scenario in software testing is …

Everyone wants to know one thing about a test suite: will it detect enough bugs?
Unfortunately, in most settings that matter, answering this question directly is impractical or …

Test coverage is sometimes used as a way to measure how thoroughly software is tested.
Coverage is used by software developers and sometimes by vendors to indicate their …

We study the relationship between three properties of test suites: size, structural coverage,
and fault-finding effectiveness. In particular, we study the question of whether achieving high …

Recently, tools for the analysis and visualization of code coverage have become widely
available. At first glance, their value in assessing and improving the quality of automated test …

A number of structural coverage criteria have been proposed to measure the adequacy of
testing efforts. In the avionics and other critical systems domains, test suites satisfying …