Defect tracing and correction<br />Defect Tracking<br />        and <br />                         correction<br />Done By...
What is defect…?<br />Q:<br />A:<br />“A defect is an operation or function that fails to meet the products specification…...
Defect discovery process…<br />The defect discovering process<br />    enables us to identify defects.<br />This process i...
Defect tracking life cycle…<br />Raising a defect<br />Reporting a defect<br />TESTER<br />Closing or reopening defect bas...
Finding Defects…<br />Every software development project plans for a set of activities that are specially designed and per...
The three category of defect finding techniques are jointly required for an effective defect management program in an orga...
Categorizing defects…<br />On the basis of<br /><ul><li>Functionality
Severity
Priority</li></li></ul><li>On the Basis of functionality<br />Interface- related<br />Navigational <br />Functional<br />
On the Basis of severity<br />High Severity<br />Medium severity<br />Low severity<br />
High Severity<br />Signifies that a major issue occurred where a function or a major system component is not working at al...
On the basis of priority…<br />High priority<br />Medium priority<br />Low priority<br />Signifies that a defect has a maj...
Acknowledging defects…<br />Acknowledging defects is common in software testing environment<br />Even though defect acknow...
Defect management process<br />The defect management process, involves defect recording, defect reporting, keeping track o...
Why to record???<br />4 purpose<br />To correct the defect<br />To report the status of the application<br />To gather sta...
Defect reporting<br />A defect report describes those which are present in the software..<br />A defect report should prov...
Contents of defect report<br />A unique identification no. for the defect.<br />The defect name and type.<br />Source of t...
Upcoming SlideShare
Loading in …5
×

Defect correction-Software Testing

2,937 views
2,759 views

Published on

Published in: Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,937
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
87
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Defect correction-Software Testing

  1. 1. Defect tracing and correction<br />Defect Tracking<br /> and <br /> correction<br />Done By : MrinmoyMukherjee<br />
  2. 2. What is defect…?<br />Q:<br />A:<br />“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”<br />
  3. 3. Defect discovery process…<br />The defect discovering process<br /> enables us to identify defects.<br />This process involves reveling <br /> defects and bringing the defect <br /> to the notice of the development team.<br />The development team then acknowledges the defect as valid and fix the defect.<br />The tester verifies and close the defect in the end.<br />
  4. 4. Defect tracking life cycle…<br />Raising a defect<br />Reporting a defect<br />TESTER<br />Closing or reopening defect based on the defect status<br /> Verifies the fixes<br />Acknowledging the defect<br />T<br />E<br />S<br />T<br />E<br />R<br />Verifies fixes internally<br />Fixing the defect<br />D<br />E<br />V<br />E<br />L<br />O<br />P<br />E<br />R<br />
  5. 5. Finding Defects…<br />Every software development project plans for a set of activities that are specially designed and performed to uncover defects.<br />There are three broad categories for detecting defects.<br />Static technique<br /> Involves performing manual intermediate checks to examine the quality of the product being developed.<br />Dynamic technique<br /> Refers to the process of executing software test to find defects.<br />Operational technique<br /> Involves end users testing the system at the operational level and discovering defects that are not identified during the testing process.<br />
  6. 6. The three category of defect finding techniques are jointly required for an effective defect management program in an organization.<br />Static<br />Dynamic<br />Operational<br />“Static technique are more effective at finding defects in the early phase of the SDLC”<br />
  7. 7. Categorizing defects…<br />On the basis of<br /><ul><li>Functionality
  8. 8. Severity
  9. 9. Priority</li></li></ul><li>On the Basis of functionality<br />Interface- related<br />Navigational <br />Functional<br />
  10. 10. On the Basis of severity<br />High Severity<br />Medium severity<br />Low severity<br />
  11. 11. High Severity<br />Signifies 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 continue<br />Medium Severity<br />Signifies 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.<br />Low Severity<br />Signifies that a minor issue occurred that costs some loss of functions. However workaround and testing can proceed without interruption. <br />
  12. 12. On the basis of priority…<br />High priority<br />Medium priority<br />Low priority<br />Signifies that a defect has a major impact on the customer. The problem should be fixed before the release of the current version in development<br />Signifies 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.<br />Signifies that a defect has a major impact on the customer. This must be immediately fixed<br />
  13. 13. Acknowledging defects…<br />Acknowledging defects is common in software testing environment<br />Even though defect acknowledgment is a crucial stage in the defect life cycle, there are often delays in the process.<br />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<br />
  14. 14. Defect management process<br />The defect management process, involves defect recording, defect reporting, keeping track of the defect using defect tracking tool.<br />Defect recording<br /> defects are identified and recorded <br /> at each stage of the testing process.<br />
  15. 15. Why to record???<br />4 purpose<br />To correct the defect<br />To report the status of the application<br />To gather statistics <br />To further improve for software development process<br />
  16. 16. Defect reporting<br />A defect report describes those which are present in the software..<br />A defect report should provide complete information on the defect to both the testing team and the team responsible for fixing the defect.<br />
  17. 17. Contents of defect report<br />A unique identification no. for the defect.<br />The defect name and type.<br />Source of the defect<br />Severity of the defect.<br />Priority assigned to the defect.<br />The current status of the defect.<br />Detailed description of the defect.<br />The platform and operating system implemented.<br />The steps performed when the defect occurs.<br />The location of the defect with screen shots.<br />The Person responsible for testing.<br />The person responsible for fixing the defect.<br />
  18. 18. Thank youf s<br />riend<br />*****<br />Its friends.. What did you think of??? <br /> <br />

×