Defect Management

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 definition. A defect, if encountered during execution, may cause a failure of the component or system.

If a Defect is appearing every time (in every execution) then that Defect is producible defect, we can provide steps for locating it.

If a Defect is some time times only appearing then that Defect is not producible defect, we have to provide proof (snap shots or database dumps) for locating it.

A tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of defects and provide reporting facilities.

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

An occurrence in which one defect prevents the detection of another.

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. lines-of code, number of classes or function points).

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

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.

Defect leakage occurs at the Customer or the End-user side after the product delivery. If the end user sees any issue in the application, then such bugs lead to Defect leakage. And this process of finding bugs is also called as Bug Leakage.

It is a testing method which proposes to raise an input signal until the system breaks down.

It ensures that the program must recover from any expected or unexpected events without loss of data or functionality. Events could be like shortage of disk space, unexpected loss of communication, or power out conditions.

Globalization testing concentrates on detecting the potential problems in the product design that could spoil globalization. It certifies that the code can handle the desired international support without breaking any functionality. And also, it ensures that there would be no data loss and display problems.

Application Lifecycle Management (ALM) is a continuous process of managing the life of Software application through development, testing and maintenance

Any mismatch that found in production phase (Customer environment).