Testing Technology Glossary-I

• Image synchronization. The process by which a playback (e.g. from CAPBAK/X and CAPBAK/MSW) holds back execution until the image or window is redrawn or found.
• In-degree. In a directed graph, the number of in-ways for a node.
• Incompatible logical branch. Two segments in one program are said to be incompatible if there is no logically feasible execution of the program which will permit both of them to be executed in the same test. See also Essential logical branch.
• Independent logical branch pair. A pair of logical branches is (sequentially) independent when there are no assignment actions along the first branch. This changes any of the variables used in the predicate of the second statement.
• Infeasible path. A logical branch sequence is logically impossible if there is no collection of setting of the input space relative to the first branch in the sequence, which permits the sequence to execute.
• Inspection/review. A process of systematically studying and inspecting programs in order to identify certain types of errors, usually accomplished by human rather than mechanical means.
• Instrumentation. The first step in analyzing test coverage, is to instrument the source code. Instrumentation modifies the source code so that special markers are positioned at every logical branch or call-pair or path. Later, during program execution of the instrumented source code, these markers will be tracked and counted to provide data for coverage reports.
• Integration Testing. Exposes faults during the process of integration of software components or software units and it is specifically aimed at exposing faults in their interactions. The integration approach could be either bottom-up (using drivers), top-down (using stubs) or a mixture of the two. The bottom up is the recommended approach.
• Interface. The informational boundary between two software systems, software system components, elements, or modules.
• Invocation point. The invocation point of a module is normally the first statement in the module.
• Invocation structure. The tree-like hierarchy that contains a link for invocation of one module by another within a software system.
• Iteration level. The level of iteration relative to the invocation of a module. A zero-level iteration characterizes flows with no iteration. A one-level iteration characterizes program flow which involves repetition of a zero-level flow.