Test Reports ppt

Test Reports 2 Contents  Handling Defects  Bug Tracking System  Test Reports  Examples 3 Handling Defects 4 Handling a defect  Analyze the defect  Report the defect  Track the defect  Retest the defect  Close the defect 5 Analyzing a defect  Is it the test, the tester, or the product?  Reproducible vs Repeatable  Can it be isolated?  Find related problems  Look for alternate paths to the problem  Is it worth reporting? 6 Handling a defect  Analyze the defect  Report the defect  Track the defect  Retest the defect  Close the defect 7 Reporting the defect  Look for duplicates  Talk with the developer  Enter it into the system  Make sure it will get noticed! 8 Characteristics of an effective defect report  Tells how to reproduce the problem  in a minimum number of steps  The report is complete and understandable  Written  Simple 9 Components of a defect report  Identifying information  Description of the problem  Various status indicators  Comments  Supporting information  Miscellaneous information 10 Components of a defect report Identifying information  Unique number  Submitter  Submit date  Program or product this is against  Version or revision of the product [...]... Description of the problem The Test Case used 28 Test Reports 29 Test Reports       Your chance to evaluate how testing went List what was tested List what was not tested, and why List still-open defects (some ask for all defects) Show the actual schedule (Test Plan) Lets management know the status of that product, from a testing standpoint, as it went out the door 30 Your Test Report    A brief... closed 22 Retesting a Defect  Retest can have 3 outcomes    The problem has indeed been fixed The problem remains A different problem shows up 23 Closing a Defect    Add Tester Notes or Verification Notes Make sure that anyone else with an interest in the problem’s resolution has a chance to test it too Close it, or recommend closure 24 Life cycle of a defect report       Entered by a tester... the fix becomes available The tester retests the problem The tester or board closes the defect 25 Bug Tracking System 26 The need for a Defect Tracking System      Facilitates clear communication about defects Allows developers to fix bugs based on priority Allows for analysis and reporting options Helps to manage the bugs Keeps a history 27 Items for your Defect Reports     Identifiers: title,... report Status indicators Severity and Priority  Severity: How “bad” is it?  Generally related to the defect’s effect on testing      High critical defect; test cannot continue Medium critical defect; test can continue with a workaround Low it’s a problem but we can keep testing Really low documentation, help files, spelling mistakes Priority: How urgent is it?  When does this have to be... defect report Status indicators Examples of Resolution status            None In Process Fixed Ready for Test Retest Not repeatable Not a problem Do Not Fix Duplicate Multiple Deferred 16 Components of a defect report Comments/Notes      Investigation Notes Resolution Notes Tester Notes Modification Notes Whatever-works-for-you Notes 17 Components of a defect report Miscellaneous fields... reproduce the problem Could be as simple as a Test Case ID, or a lengthy procedure Pay attention to problems that are merely repeatable or not reproducible 18 Components of a defect report Miscellaneous fields (2)             Environment Target Release Closed Release Closed Date Owner Tester Discovered by Defect type Software component affected Fix hours Test hours Workarounds 19 Components of...     Error printouts Screen shots The test case itself A diskette with data or files Memory dump Trace files, error logs, etc 20 Handling a defect      Analyze the defect Report the defect Track the defect Retest the defect Close the defect 21 Tracking a Defect     Must have a process in place Generally done by some sort of Review Board The lead tester should be on that board The purpose... Report    A brief description of what you did, when An attached list of all the Test Cases with an indication of which ones passed and which ones failed (and by default, then, which ones didn’t get run) A list of all the defects found (a list of Brief Descriptions) 31 Examples 32 Examples   Test Report template Test Report example 33 ... acknowledged or explained in the Description Description 11 Components of a defect report Description of the problem Contents         The problem itself  What did happen  What should have happened The test case used Any other helpful information whatsoever  In particular, any attachments Keep it to 3 or 4 sentences if you can Avoid vague or confusing terms (“frequently”, “sometimes”) Avoid uncommon . Test Reports 2 Contents  Handling Defects  Bug Tracking System  Test Reports  Examples 3 Handling Defects 4 Handling a defect . defect’s effect on testing  High critical defect; test cannot continue  Medium critical defect; test can continue with a workaround  Low it’s a problem but we can keep testing  Really low. Analyze the defect  Report the defect  Track the defect  Retest the defect  Close the defect 5 Analyzing a defect  Is it the test, the tester, or the product?  Reproducible vs Repeatable  Can