Software Testing Glossary - Software Testing as a Service - page 178

Boundary value: An input value or output value which is on the edge of an equiva-
lence partition or at the smallest incremental distance on either side of an edge, for
example the minimum or maximum value of a range.
Boundary value analysis: A black box test design technique in which test cases are
designed based on boundary values.
Boundary value coverage: The percentage of boundary values that have been exer-
cised by a test suite.
Boundary value testing: See boundary value analysis .
Branch: A basic block that can be selected for execution based on a program con-
struct in which one of two or more alternative program paths are available (e.g.,
case, jump, go to, if then-else).
Branch condition: See condition .
Branch condition combination coverage: See multiple-condition coverage .
Branch condition combination testing: See multiple-condition testing .
Branch condition coverage: See condition coverage .
Branch coverage: The percentage of branches that have been exercised by a test
suite. 100% branch coverage implies both 100% decision coverage and 100% state-
ment coverage.
Branch testing: A white box test design technique in which test cases are designed
to execute branches.
Bug: See defect .
Bug report: See defect report.
Business process-based testing: An approach to testing in which test cases are
designed based on descriptions and/or knowledge of business processes.
C
Capability Maturity Model (CMM): A five level staged framework that describes
the key elements of an effective software process. The Capability Maturity Model
covers best practices for planning, engineering, and managing software develop-
ment and maintenance. [CMM]
Capability Maturity Model Integration (CMMI): A framework that describes
the key elements of an effective product development and maintenance process.
The Capability Maturity Model Integration covers best practices for planning,
engineering, and managing product development and maintenance. CMMI is the
designated successor of the CMM. [CMMI]
Capture/playback tool: A type of test execution tool where inputs are recorded during
manual testing in order to generate automated test scripts that can be executed later
(i.e., replayed). These tools are often used to support automated regression testing.
Capture/replay tool: See capture/playback tool .
CASE: Acronym for Computer Aided Software Engineering.
CAST: Acronym for Computer Aided Software Testing. See also test automation .