Jargons used in Testing / Development

mutation testing

A testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations.

loopback testing

Testing in which signals or data from a test device are input to a system or component, and results are returned to the test device for measurement or comparison.

 back-to-back testing

Testing in which two or more variants of a program are executed with the same inputs, the outputs are compared, and errors are analyzed in case of discrepancies. See also: mutation testing.

 interface testing

Testing conducted to evaluate whether systems or components pass data and control correctly to one another. See also: component testing; integration testing; system testing; unit testing.

 big-bang testing

A type of integration testing in which software elements, hardware elements, or both are combined all at once into an overall system, rather than in stages.

 qualification testing

Testing conducted to determine whether a system or component is suitable for operational use. See also: acceptance testing; development testing; operational testing.

 operational testing

Testing conducted to evaluate a system or component in its operational environment. Contrast with: development testing. See also: acceptance testing; qualification testing

 acceptance testing

Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a system or component. Contrast with: development testing. See also: operational testing; qualification testing.

 System Testing

Testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements. See also: component testing; integration testing; interface testing; unit testing.

 Unit testing

Testing of individual hardware or software units or groups of related units. See also: component testing; integration testing; interface testing; system testing.

 Stress testing

Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements.

 Performance testing

Testing conducted to evaluate the compliance of a system or component with specified performance requirements. See also: functional testing.

 Regression testing

Selective retesting of a system or component to verify that modifications have not caused unintended effects and that the system or component still complies with its specified requirements.

 Integration testing

Testing in which software components, hardware components, or both are combined and tested to evaluate the interaction between them. See also: component testing; interface testing; system testing; unit testing.

 Structural Testing/Clear box testing/White box testing

Testing that takes into account the internal mechanism of a system or component. Types include branch testing, path testing, statement testing. Syn: glassbox testing; white-box testing. Contrast with: functional testing (1).

 Functional testing/Black box testing

Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions. Syn: blackbox testing. Contrast with: structural testing.

Testing conducted to evaluate the compliance of a system or component with specified functional requirements. See also: performance testing.

 Validation

The process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements. Contrast with: verification.

 Verification

The process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. Contrast with: validation.

 Formal review techniques

• Requirements review
• Design review
• Code review
• Test readiness review
• Formal qualification review