Defect Handling

Defect Handling

What is Defect?

·       Defect is a coding error in a computer program.

·       A software error is present when the program does not do what its end user expects it to do.

Who can report a Defect?

     Anyone who has involved in software development life cycle and who is using the software can report a Defect. In most of the cases defects are reported by Testing Team.

A short list of people expected to report bugs:

1. Testers / QA Engineers
2. Developers
3. Technical Support
4. End Users
5. Sales and Marketing Engineers

Defect Reporting

• Defect or Bug Report is the medium of communication between the  tester and the programmer
•  Provides clarity to the management, particularly at the summary level
•  Defect Report should be accurate, concise, thoroughly-edited, well conceived, high-quality technical document 
•  The problem should be described in a way that maximizes  the probability that it will be fixed
•  Defect Report should be non-judgmental and should not point finger at the programmer
•  Crisp Defect Reporting process improves the test team’s communications with the senior and peer management

Defect Life Cycle

§  Defect Life Cycle helps in handling defects efficiently.

§  This DLC will help the users to know the status of the defect.

 

                                                                                                     

		Yes s

 

                                                                                               No

			Yes s

 

Types of Defects

1. Cosmetic flaw
2. Data corruption
3. Data loss
4. Documentation Issue
5. Incorrect Operation
6. Installation Problem
7. Missing Feature
8. Slow Performance
9. System Crash
10. Unexpected Behavior
11. Unfriendly behavior

How do u decide the Severity of the defect

Severity Level	Description	Response Time or Turn-around Time
High	A defect occurred due to the inability of a key function to perform.  This problem causes the system hang it halts (crash), or the user is dropped out of the system. An immediate fix or work around is needed from development so that testing can continue.	Defect should be responded to within 24 hours and the situation should be resolved test exit
Medium	A defect occurred which severely restricts the system such as the inability to use a major function of the system. There is no acceptable work-around but the problem does not inhibit the testing of other functions	A response or action plan should be provided within 3 working days and the situation should be resolved before test exit.

Severity Level	Description	Response Time or Turn-around Time
Low	A defect is occurred which places minor restrict on a function that is not critical. There is an acceptable work-around for the defect.	A response or action plan should be provided within 5 working days and the situation should be resolved before test exit.
Others	An incident occurred which places no restrictions on any function of the system. No immediate impact to testing. A Design issue or Requirements not definitively detailed in project. The fix dates are subject to negotiation.	An action plan should be provided for next release or future enhancement

Defect Severity VS Defect Priority

• The General rule for the fixing the defects will depend on the Severity.
• All the High Severity Defects should be fixed first.
• This may not be the same in all cases some times even though severity of the bug is high it may not be take as the High priority.
• At the same time the low severity bug may be considered as high priority.

Defect Tracking Sheet

Defect No	Description	Origin	Severity	Priority	Status
Unique No	Dec of Bug	Birth place of the Bug	Critical Major Medium Minor Cosmetic	High Medium Low	Submitted Accepted Fixed Rejected Postponed Closed

Defect Tracking Tools

§  Bug Tracker -- BSL Proprietary Tools

• Rational Clear Quest
• Test Director

3.8 Gap Analysis:

                

1. BRS Vs SRS

BRS	SRS	Test Case	Defects
BRS001	SRS001	TC001	Defect001
			Defect002
		TC002
		TC003
	SRS002
	SRS003

          BRS01 – SRS01

                         -SRS02

                         -SRS03

2. SRS Vs TC

          SRS01 – TC01

                       - TC02

                       - TC03

3. TC Vs Defects

           TC01 –  Defects01

           --  Defects02

3.9 Deliverables:

All the documents which are prepared in each and every stage.

• FRS
• SRS
• Use Cases
• Test Plan
• Defect Report
• Review Report etc.