software testing terms part 3
Software testing terms 3
Capability Maturity Model Integration (CMMI):
A framework that describes the key elements of an effective product development and maintenance process. The Capability Maturity Model Integration covers best-practices for planning, engineering and managing product development and maintenance. CMMI is the designated successor of the CMM. [CMMI] See also Capability Maturity Model (CMM).
A type of test execution tool where inputs are recorded during manual testing in order to generate automated test scripts that can be executed later (i.e. replayed). These tools are often used to support automated regression testing.
Acronym for Computer Aided Software Engineering.
Acronym for Computer Aided Software Testing. See also test automation. causal analysis: The analysis of defects to determine their root cause.
A graphical representation used to organize and display the interrelationships of various possible root causes of a problem. Possible causes of a real or
potential defect or failure are organized in categories and subcategories in a horizontal tree-structure, with the (potential) defect or failure as the root node. [After Juran]
cause-effect graph: A graphical representation of inputs and/or stimuli (causes) with their associated outputs (effects), which can be used to design test cases.
cause-effect graphing: A black box test design technique in which test cases are designed from cause-effect graphs.
certification: The process of confirming that a component, system or person complies with its specified requirements, e.g. by passing an exam.
change control: See configuration control.
change control board: See configuration control board.change management: (1) A structured approach to transitioning individuals, teams, and organizations from a current state to a desired future state. (2) Controlled way to effect a change, or a proposed change, to a product or service. See also configuration management.
changeability: The capability of the software product to enable specified modifications to be implemented. [ISO 9126] See also maintainability.
charter: See test charter. checker: See reviewer.
checklist-based testing: An experience-based test design technique whereby the experienced tester uses a high -level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified. See also experience-based testing.
Chow’s coverage metrics: See N-switch coverage.
classification tree: A tree showing equivalence partitions hierarchically ordered, which is used to design test cases in the classification tree method. See also classification tree method.
classification tree method: A black box test design technique in which test cases, describedby means of a classification tree, are designed to execute combinations of representatives of input and/or output domains. [Grochtmann]
clear-box testing: See white-box testing.
code: Computer instructions and data definitions expressed in a programming language or in a form output by an assembler, compiler or other translator.
code analyzer: See static code analyzer.
code coverage: An analysis method that determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed, e.g. statement coverage, decision coverage or condition coverage.
code-based testing: See white box testing.
codependent behavior: Excessive emotional or psychological dependence on another person, specifically in trying to change that person’s current (undesirable) behavior while supporting them in continuing that behavior. For example, in software testing, complaining about late delivery to test and yet enjoying the necessary “heroism” working additional hours to make up time when delivery is running late, therefore reinforcing the lateness.
co-existence: The capability of the software product to co-exist with other independent software in a common environment sharing common resources.
commercial off-the-shelf software: See off-the-shelf software. comparator: See test comparator.
compatibility testing: See interoperability testing.
compiler: A software tool that translates programs expressed in a high order language into their machine language equivalents.
complete testing:See exhaustive testing. completion criteria: See exit criteria.
complexity: The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify.
compliance: The capability of the software product to adhere to standards, conventions or regulations in laws and similar prescriptions. [ISO 9126]
compliance testing: The process of testing to determine the compliance of the component or system.
component: A minimal software item that can be tested in isolation.
component integration testing: Testing performed to expose defects in the interfaces and interaction between integrated components.
component specification: A description of a component’s function in terms of its output values for specified input values under specified conditions, and required non-functional behavior (e.g. resource-utilization).
component testing: The testing of individual software components.
compound condition: Two or more single conditions joined by means of a logical operator (AND, OR or XOR), e.g. ‘A>B AND C>1000’.
concrete test case: See low level test case.
concurrency testing: Testing to determine how the occurrence of two or more activities within the same interval of time, achieved either by interleaving the activities or by simultaneous execution, is handled by the component or system.
condition: A logical expression that can be evaluated as True or False, e.g. A>B. See also test condition.
condition combination coverage: See multiple condition coverage. condition combination testing: See multiple condition testing.
configuration management: A discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements.
– N = the number of nodes in a graph
– P = the number of disconnected parts of the graph (e.g. a called graph or subroutine) [After McCabe]
QTP Online Training