Defect-Based Software Testing Technique
A Defect-Based Testing Technique is a technique where test cases are derived from defects. Instead of using traditional requirements documents or use cases (Specification-based techniques), this strategy bases its test cases on defects.
A categorized list of Defects (called a Defect Taxonomy) is being used. The coverage using this technique is not very systematic, so deriving the base of your test cases only from this technique may not solve the purpose of the quality deliverable.
This technique can complement your test-deriving conditions and can be one option to increase testing coverage. Or in some other sense – This technique can be applied when all the test conditions and test cases are identified and we need some extra coverage or insight into testing.
The defect-based technique can be used at any level of testing, but it is best suited to Systems Testing. We should base our test cases on the available defect taxonomies as well. These defects can be the production ones or historical ones. Root cause analysis can also be used to baseline your test cases.
The 5 step plan to write the test cases through Defect based testing techniques can be:
- Identify and prioritize the Requirements
- Identify and collect all the Defects
- Brainstorm on the Defect
- Link the Defect to the Requirement
- Write the Test conditions/Test cases based on the linked Defects.
Was this helpful?
Recommended Reading
-
Introduction to Defect Management Process: The more focused process and testing will allow less buggy software in the market. Defect Prevention is much more efficient and effective in reducing the number of defects and also is very cost effective to fix the defects found during the early stage of the…
-
This article is an extensive and all-in-one guide to Defect Density. We will see its importance and how to calculate it. Let's get started. Test Metrics can be tricky. They are the only way to measure yet the variety is overwhelming. You could be collecting something that isn’t giving you…
-
In this article, we discuss in detail how to reproduce a non-reproducible defect and make the testing worth it. In the world of software testing, a defect once found should be consistently reproducible so the tester can report with conviction, a developer can fix with clarity and the QA team…
-
Here is an article on effective Defect Prevention Approaches and Critical Views: Quality Assurance is the term that is commonly used to address the testing teams in IT projects. Technicalities aside, quality assurance activities are not just targeted at defect identification (which is finding defects after they have happened). This…
