Term
|
Definition
| The code itself is ignored; the only information used in drawing up test cases is in the specification document. Exhaustive black-box testing is impossible in practice because there can easily be too many test cases to consider. |
|
|
Term
|
Definition
if(x >= 0)
y = computeSquareRoot(x, errorFlag); computeSquareRoot is never invoked unless the value of x is non-negative. The artifact can never be tested with negative values of x to see if it behaves correctly. |
|
|
Term
| Fourth generation language (4GL) |
|
Definition
| Each statement is equivalent to 40 or 50 machine instructions. 4GL products are shorter and quicker to develop and easier to maintain. |
|
|
Term
|
Definition
| Code and test each artifact separately, link together all artifacts, and test the product as a whole. |
|
|
Term
|
Definition
| Running a series of tests to ensure that all branches are tested at least once. |
|
|
Term
|
Definition
|
|
Term
|
Definition
| Running a series of test cases during which every statement is executed at least once. |
|
|
Term
|
Definition
| A code artifact that calls a module one or more times, if possible checking values returned by the artifact under test. |
|
|
Term
|
Definition
| An empty artifact. Could return values corresponding to preplanned test cases. |
|
|
Term
|
Definition
| Testing an artifact as soon as it is coded. |
|
|
