Defect management

The process of obtaining user account information based on trial and error with the intention of using that information in a security attack.

Any condition that deviates from expectation based on requirements specifications, design documents, user documents, standards, etc., or from someone's …

Defect density of a component of the test automation code.

The process of intentionally adding defects to those already in the component or system for the purpose of monitoring the rate of detection and removal, and …

A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g., an incorrect statement or data …

An approach to testing in which gamification and awards for defects found are used as a motivator.

A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function.

A system of (hierarchical) categories designed to be a useful aid for reproducibly classifying defects.

An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes, it is hoped that the likelihood of …

A graphical representation used to organize and display the interrelationships of various possible root causes of a problem. Possible causes of a real or …

The total costs incurred on quality activities and issues and often split into prevention costs, appraisal costs, internal failure costs and external failure …

A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute …

The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms, e.g., …

The number of defects found by a test level, divided by the number found by that test level and any other means afterwards.

The process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying them and identifying the impact.

A cross-functional team of stakeholders who manage reported defects from initial detection to ultimate resolution (defect removal, defect deferral, or report …

A procedure to derive and/or select test cases targeted at one or more defect types, with tests being developed from what is known about the specific defect …

Any event occurring that requires investigation.

A document reporting on any event that occurred, e.g., during the testing, which requires investigation.

A human action that produces an incorrect result.

A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a …

A tool for seeding (i.e., intentionally inserting) faults in a component or system.

The degree to which a component or system can continue normal operation despite the presence of erroneous inputs.

A defect that was not detected in a previous test level which is supposed to find such type of defects.

Deviation of the component or system from its expected delivery, service or result.

The physical or functional manifestation of a failure.

A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence.

The ratio of the number of failures of a given category to a given unit of measure, e.g., failures per unit of time, failures per number of transactions, …

A test result in which a defect is reported although no such defect actually exists in the test object.

A test result which fails to identify the presence of a defect that is actually present in the test object.

The process of intentionally adding defects to a system for the purpose of finding out whether the system can detect, and possibly recover from, a defect. Fault …

The capability of the software product to maintain a specified level of performance in cases of software faults (defects) or of infringement of its specified …

A technique used to analyze the causes of faults (defects). The technique visually models how logical relationships between failures, human errors, and …

A tool that facilitates the recording and status tracking of incidents. They often have workflow-oriented facilities to track and control the allocation, …

(1) The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. (2) The capability of the software …

The average time a component or system will take to recover from a failure.

A memory access failure due to a defect in a program's dynamic store allocation logic that causes it to fail to release memory after it has finished using it, …

The level of (business) importance assigned to an item, e.g., defect.

The person who records each defect mentioned and any suggestions for process improvement during a review meeting, on a logging form. The scribe should ensure …

The capability of the software product to re-establish a specified level of performance and recover the data directly affected in case of failure.

The process of identifying risks using techniques such as brainstorming, checklists and failure history.

A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.

A set of steps required to implement the security policy and the steps to be taken in response to a security incident.

The degree of impact that a defect has on the development or operation of a component or system.

A tool that provides support to the test management and control part of a test process. It often has several capabilities, such as testware management, …

The degree to which a component or system protects users against making errors.