Glossary

black-box testing.

A testing approach whereby the program is considered as a complete entity and the internal structure is ignored. Test data are derived solely from the application's specification.

bottom-up testing.

A form of incremental module testing in which the terminal module is tested first, then its calling module, and so on.

boundary-value analysis.

A black-box testing methodology that focuses on the boundary areas of a program's input domain.

branch coverage.

See decision coverage.

cause-effect graphing.

A technique that aids in identifying a set of high-yield test cases by using a simplified digitallogic circuit (combinatorial logic network) graph.

code inspection.

A set of procedures and error-detection techniques used for group code readings that is often used as part of the testing cycle to detect errors. Usually a checklist of common errors is used to compare the code against.

condition coverage.

A white-box criterion in which one writes enough test cases that each condition in a decision takes on all possible outcomes at least once.

data-driven testing.

See black-box testing.

decision/condition coverage.

A white-box testing criterion that requires sufficient test cases that each condition in a decision takes on all possible outcomes at least once, each decision takes on all possible outcomes at least once, and each point of entry is invoked at least once.

decision coverage.

A criterion used in white-box testing in which you write enough ...

Get The Art of Software Testing, Second Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.