|Software Testing Glossary Series|CTFL|C|

Checklist-Based Reviewing:

Checklist-Based Reviewing is a walk-through/review technique led by a list of questions or required attributes.

Checklist-Based Testing:

Checklist-Based Testing is an experience-based test technique where the experienced tester uses their experience to create 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.

Code Coverage:

Code Coverage is an analysis method that decides 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.

Commercial Off-The-Shelf (COTS):

Commercial Off-The-Shelf (COTS) is a software product which is developed for the open market, in other words, for a large number of customers, and that is delivered to many customers in identical format.

Compatibility:

Compatibility is the level to which a component/module or system can exchange information with other components or systems.

Compliance:

Compliance is the capability of the software product to stick to standards, conventions or regulations in laws and similar prescriptions.

Component:

An individual/lowest part of a system that can be tested in isolation.

Component Integration Testing:

Component Integration Testing performed to find defects in the interfaces and interactions between integrated components. This is also known as Link Testing.

Component specification:

Component Specification is the description of a component's functionality in terms of its output values for specified input values under specified conditions, and required non-functional behavior.

Component Testing:

Component Testing is the testing of individual hardware or software components. This is also known as module testing or unit testing.

Condition:

Condition is some logical expression that can be evaluated as True or False,

Configuration:

Configuration is the composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.

Configuration Item:

Configuration Item is an aggregation of work products that is designed for configuration management and treated as a single entity in the configuration management process.

Configuration Management:

Configuration Management is a process to 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.

Configuration Management Tool:

Configuration Management Tool is a tool which provides support for the identification and control of configuration items, their status over changes and versions, and the release of baselines.

Confirmation Testing:

Confirmation testing is also known as re-testing which conducts after fixing defects with the motive to confirm that reported failures/defects does not occur anymore.

Contractual Acceptance Testing:

Contractual Acceptance Testing is the testing which is conducted to verify that the functionality is working as per the agreement.

Control Flow:

Control Flow is the sequence in which operations are performed during the execution of a test item.

Cost of Quality:

Cost of Quality is the total cost incurred on quality activities and issues also include the cost of those activities which performed to prevent the failures. This cost also includes internal and external failure cost(s).

Coverage:

Coverage is the scope to which specified items have been determined or have been performed by a test suite expressed as a percentage.

Coverage Item:

Coverage Item is an attribute or combination of attributes that is derived from one or more test conditions by using a test technique that enables the measurement of the thoroughness of the test execution.

Coverage Tool:

Coverage Tool is a tool that provides measures through which structural elements, e.g., statements, branches have been performed by a test suite.

References:
ISTQB
Wikipedia