Software Testing Glossary

Black Box Testing is testing for compliance with software requirements without knowing the internal structure of the system implementation.

The test scenario that cannot be completed because of failure of preconditions.

Consistent approach to integration testing, in which lower-level components are tested first and then used to facilitate software testing of components at higher levels.

Input or output value, which is on the verge of an equivalent area or at the least distance from both sides of the verge, such as minimum or maximum value of the area.

Development of tests using a black box, in which test cases are designed on the basis of boundary values.

Percentage of boundary values that have been tested by a set of tests. 

Software testing technique in which tests are designed to include representatives of boundary values.

Mainframe, which can be selected for execution, based on the logical structure of the program, in which is accessible one of two or more alternative paths, for example, case, jump, go to, if then-else.

Percentage of branches that have been executed by test suite. 100% coverage of branches presupposes 100% statement and decision coverage.

Development of tests by white box method, in which test cases are designed in order to execute branches.