Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Defect Management

Download as pdf or txt
Download as pdf or txt
You are on page 1of 15

Defect

management
Introduction
• Process of recognizing, investigating,
taking action(decision making) and
disposing of defects.
• It involves recording, classifying them
and identifying their impacts
Defect Life Cycle
Severity and Priority
• Severity: It is the extent to which the defect can
affect the software. It can be of following types
1. Critical
2. Major
3. Moderate
4. Minor
• Priority: The order in which we should resolve a
defect. It can be of following types:
1. High
2. Medium
3. Low
Types of Defects
1. User interface defects
2. Error Handling defects
3. Input domain defects
4. Manipulations defects
5. Race condition defects
6. Source defects
7. ID control defects
8. H/w related defects
9. Load condition defects
Defect Classification
Defect may be classified in Different ways under different schemes.
1. Requirement-related defects may be further classified as
Functional Defect
Interface Defect
2. Design related defect may be classified as follows-
Algorithm Defect
Module –Interface Defect
System –Interface Defect
User –Interface Defect
3. Coding Defect
Variable Declaration/Initialization Defect
Database-Related Defect
Commenting/Documenting Defect
4. Testing Defect
Test-Design Defect
Test-Environment Defect
Test-Tool Defect
Defect Management
Defect fixing
Defect Report Template
Techniques for finding defects
1. Static Techniques: Desk checking/ Verification. Reviews,
Walkthroughs, Inspection, and Audits, Reviewed with Checklist,
Standards, and other artifacts, Knowledge and experience.
2. Dynamic Testing: Its validation technique , which includes dummy
or actual execution of work products to evaluate it with expected
behavior. i.e. system testing, Unit Testing, This evaluates the
product with respect to requirements defined , designs created
and mark it as pass or fail – fitness for use.
3. Operational Techniques: Include auditing work products and
projects to understand whether the processes defined for
development /testing are being followed correctly or not.
Whether they are effective or not, it also revisits the defects
before and after fixing any analysis. Smoke testing, Sanity testing.
1.
Questions
Defect reports are useful as they contain
a) defect description
b) Priority
c) Summary
d) Name of tester
e) All of the above
2. What is not true about priority?
a) Priority is impact of defect on business
b) Priority can be urgent,high,medium,low
c) Priority once assigned can not be changed.
d) All of the above
3. Who determines the severity of bug?
a) Developer
b) Customer
c) Tester
d) All stakeholders
4. Severity can be changed at any point of time .True or false.
a) True
b) False
5) Which of the following stage is performed by by developer?
1. New
2. Open
3. Assigned
4. Fixed
5. Verify
6. Closed
7. Deferred
8. Rejected
a) 1,2,3,4,5,6
b) 2,3,4,5,6,7,8
c) 2,3,4,7,8
d) 2,3,4,5,6

You might also like