This document discusses defect tracking and correction in software development. It defines a defect as any non-conformity to specifications. The defect discovery process involves identifying defects and notifying the development team. The developer then acknowledges, fixes, and verifies the defect. Defects go through a tracking lifecycle of being raised, reported, fixed, and closed. Defects are found through static, dynamic, and operational techniques and categorized by functionality, severity, and priority. The document outlines the contents of a defect report and explains the purpose of defect recording and reporting in the defect management process.

1. Defect tracing and correctionDefect Tracking and correctionDone By : MrinmoyMukherjee

2. What is defect…?Q:A:“A defect is an operation or function that fails to meet the products specification…. To be precise a defect is any non-conformity in a software product or process”

3. Defect discovery process…The defect discovering process enables us to identify defects.This process involves reveling defects and bringing the defect to the notice of the development team.The development team then acknowledges the defect as valid and fix the defect.The tester verifies and close the defect in the end.

4. Defect tracking life cycle…Raising a defectReporting a defectTESTERClosing or reopening defect based on the defect status Verifies the fixesAcknowledging the defectTESTERVerifies fixes internallyFixing the defectDEVELOPER

5. Finding Defects…Every software development project plans for a set of activities that are specially designed and performed to uncover defects.There are three broad categories for detecting defects.Static technique Involves performing manual intermediate checks to examine the quality of the product being developed.Dynamic technique Refers to the process of executing software test to find defects.Operational technique Involves end users testing the system at the operational level and discovering defects that are not identified during the testing process.

6. The three category of defect finding techniques are jointly required for an effective defect management program in an organization.StaticDynamicOperational“Static technique are more effective at finding defects in the early phase of the SDLC”

7. Categorizing defects…On the basis ofFunctionality

8. Severity

9. PriorityOn the Basis of functionalityInterface- relatedNavigational Functional

10. On the Basis of severityHigh SeverityMedium severityLow severity

11. High SeveritySignifies that a major issue occurred where a function or a major system component is not working at all. There is no workaround and testing cannot continueMedium SeveritySignifies that a major issue occurred where a function or a major system component is not working properly. However there is a workaround and testing can continue.Low SeveritySignifies that a minor issue occurred that costs some loss of functions. However workaround and testing can proceed without interruption.

12. On the basis of priority…High priorityMedium priorityLow prioritySignifies that a defect has a major impact on the customer. The problem should be fixed before the release of the current version in developmentSignifies that a defect has a minor impact on the customer. The flaw should be fixed if there is time, but it can be deferred until the next release.Signifies that a defect has a major impact on the customer. This must be immediately fixed

13. Acknowledging defects…Acknowledging defects is common in software testing environmentEven though defect acknowledgment is a crucial stage in the defect life cycle, there are often delays in the process.One of the prominent reasons for delays in the acknowledgment of the defect is when the testing team is unable to replicate the defect report for the development team

14. Defect management processThe defect management process, involves defect recording, defect reporting, keeping track of the defect using defect tracking tool.Defect recording defects are identified and recorded at each stage of the testing process.

15. Why to record???4 purposeTo correct the defectTo report the status of the applicationTo gather statistics To further improve for software development process

16. Defect reportingA defect report describes those which are present in the software..A defect report should provide complete information on the defect to both the testing team and the team responsible for fixing the defect.

17. Contents of defect reportA unique identification no. for the defect.The defect name and type.Source of the defectSeverity of the defect.Priority assigned to the defect.The current status of the defect.Detailed description of the defect.The platform and operating system implemented.The steps performed when the defect occurs.The location of the defect with screen shots.The Person responsible for testing.The person responsible for fixing the defect.

18. Thank youf sriend*****Its friends.. What did you think of??? 