Defect Management
Defects determine the effectiveness of the Testing what we do. If there are no defects, it directly implies that we don’t have our job. There are two points worth considering here, either the developer is so strong that there are no defects arising out, or the test engineer is weak. In many situations, the second is proving correct. This implies that we lack the knack. In this section, let us understand Defects.
What is a Defect?
For a test engineer, a defect is following: -
• Any deviation from specification
• Anything that causes user dissatisfaction
• Incorrect output
• Software does not do what it intended to do.
Bug / Defect / Error: -
• Software is said to have bug if it features deviates from specifications.
• Software is said to have defect if it has unwanted side effects.
• Software is said to have Error if it gives incorrect output.
But as for a test engineer all are same as the above definition is only for the purpose of documentation or indicative.
Defects determine the effectiveness of the Testing what we do. If there are no defects, it directly implies that we don’t have our job. There are two points worth considering here, either the developer is so strong that there are no defects arising out, or the test engineer is weak. In many situations, the second is proving correct. This implies that we lack the knack. In this section, let us understand Defects.
What is a Defect?
For a test engineer, a defect is following: -
• Any deviation from specification
• Anything that causes user dissatisfaction
• Incorrect output
• Software does not do what it intended to do.
Bug / Defect / Error: -
• Software is said to have bug if it features deviates from specifications.
• Software is said to have defect if it has unwanted side effects.
• Software is said to have Error if it gives incorrect output.
But as for a test engineer all are same as the above definition is only for the purpose of documentation or indicative.
Post a Comment