Construct · 1 fields · 1 citations

test adequacy criteria: a standalone construct

One name. One construct. A landmark on the map.

● anchor · a standalone construct Nearest construct by meaning·not indexed
test adequacycriteria1 CONSTRUCTTest adequacy criteriaZHU · SOFTWARE ENGINEERING

A single standalone construct; nearby constructs are located against it in the Collider. Tap a field for its definition, unit, and measures.

Software engineering

rules that define when a test set is adequate, such as statement, branch or data-flow coverage, compared by their strength.

In software engineering, test adequacy criteria refers to rules that define when a test set is adequate, such as statement, branch or data-flow coverage, compared by their strength. This meaning comes from Zhu (1997) in ACM Computing Surveys.[1]

Unit
Recovery means
Measured by

Next

Run it through the Collider, or take the citations with you.

See how test adequacy criteria sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in ColliderExport BibTeXReport this entry

Nearby constructs

test adequacy criterion1 fields · 1 citationsanchor · a standalone constructcoverage3 fields · 3 citationsjingle · one word, three constructsstrength4 fields · 6 citationsjingle · one word, four constructs

References

  1. Zhu, H., Hall, P. A. V., & May, J. H. R. (1997). Software unit test coverage and adequacy. ACM Computing Surveys, 29(4), 366-427. https://doi.org/10.1145/267580.267590

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct