low-level test case
A test case with concrete values for preconditions, input data, expected results, postconditions, and a detailed description of actions (where applicable).
A test case with concrete values for preconditions, input data, expected results, postconditions, and a detailed description of actions (where applicable).
A test plan that typically addresses one test level. See also test plan.
The capability of the software product to interact with one or more specified components or systems. [After ISO 9126] See also Functionality.
Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. See also Component integration testing, system integration testing.
Testing performed by people who are co-located with the project team but are not fellow employees.
A review not based on a formal (documented) procedure.
A test case without concrete (implementation level) values for input data and expected results. Logical operators are used: instances of the actual values are not yet defined and/or available. See Also: low-level test case Synonyms: logical test case, abstract test case
A generally recognized rule of thumb that helps to achieve a goal.
The capability of the software product to provide functions which meet stated and implied needs when the software is used under specified conditions. [ISO 9126]
A review characterized by documented procedures and requirements, e.g. inspection.