Writing Effective Bug Report - BugDay Bangkok 2012


Published on

Published in: Technology
  • Be the first to comment

Writing Effective Bug Report - BugDay Bangkok 2012

  1. 1. Writing Effective Bug Reports
  2. 2. 1: Know Your Audience(s)
  3. 3. first audience: the person whomust fix the bug
  4. 4. second audience: the person orgroup who decides
  5. 5. 2: Choose a Good Title
  6. 6. Examples:- Program crashes when you choose exit from the filemenu just after the database has become unavailableand you were saving changes to a record- Program crashes- Problem when database offline- Crash on exit after timeout
  7. 7. 3: WriteClear, Unambiguous Steps
  8. 8. Step:-1. Launch the client 1. Launch the client2. Call up a record 2. Query the database for3. Change the record but new entriesdon’t save your changes yet 3. Launch a browser4. Take the database server 4. Read the news onoffline yahoo.com5. Attempt to save the record 5. Quit the browser6. Receive a timeout error 6. Choose an entry7. Exit the client 7. Change the category fromResult: Crash “vegetable” to “fruit” 8. Take the database offline 9. Attempt to save the record 10. Receive a timeout error 11. Exit the client Result: Crash
  9. 9. 4: Explain the Effectof the Bug, Not Just the Symptoms
  10. 10. Examples:1. A report that “an annoying dialog prevents you fromclosing application”2. A report that “the application hangs on exit”
  11. 11. Defect Report Templete:-Bug Name: Application crash on clicking the SAVE button while creating a new user.Area Path: USERS menu > New UsersBuild Number: Version Number 5.0.1Severity: HIGH (High/Medium/Low) Priority: HIGH (High/Medium/Low) Assigned to: Developer-XReported By: Your NameReported On: DateStatus: New/Open/Active (Depends on the Tool you are using)Environment: Windows 2003/SQL Server 2005Description:...Steps To Reproduce:1) ...2) ...Expected result: ...(Attach ‘application crash’ screen shot.. IF any)