Software Testing Glossary

Software developed specifically for the group of users or customers. The opposite of it is complete software.

Best or innovative method which can improve the performance of organizations in the given conditions and is generally recognized as the best by other similar organizations.

Operational testing performed by potential and / or existing clients / customers on the outside, does not contact the developers, in order to determine whether a component or system satisfies the requirements of the client / customer and fits into business processes. 

Type of integration testing, in which hardware or software elements, or both, are going to a component or an entire system not in stages, but at once.

Technique that tests an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

Process of test cases’ creation and/or choice based on the analysis of component or system functional and non-functional specifications not knowing its internal structure.

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.