Archive
Archive for January, 2012
Defect Management
January 3, 2012
Leave a comment
Defect: It is any flow in the software system. It can be classified into
- Wrong
- Missing
- Extra
Examples of defects:
- Wrong or incomplete requirements
- Incorrect design specification
- Incorrect program specification
- Errors in coding
- Data entry errors
- Errors in testing
- Mistakes in error correction
Error: A human action that produces an incorrect result
Fault: (Defect) may lead to failure
Failure: malfunction of software
Severity: It indicates how bad the bug is and reflects its impact to the product and to the user. It should be predefined for consistency
Ex. Misspelling on a screen, Broken link in help, Misspelling on an error message
Priority: It determines the order they can be fixed. It can be decided in 4 levels as follows:
- Very High
- High
- Medium
- Low
Defect report attributes:
- Defect Id
- Project Name
- Module Name
- Sub-module Name
- Phase
- Type
- Severity
- Priority
- Summary
- Description
- Status
- Reported by
- Assigned to
- CC to
Defect Tracking Tools
- Test Director (or QC)
- Rational clear quest
- Bugzilla
- Excel sheet
Defect Management Process
- Defect Prevention
- Deliverable base-ling (sticking to requirements)
- Defect Naming
- Defect Resolution
- Process Improvement (root cause analysis
- Management Reporting
Categories: Software Testing Fundamental