Writing EffectiveBug Reports

1: Know Your Audience(s)

first audience: the person  who must fix the bug

second audience: the person or group who decides

2: Choose a Good Title

Examples:

-  Program crashes when you choose exit from the file menu just after the database has become unavailable and you were saving changes to a record

- Program crashes

- Problem when database offline

- Crash on exit after timeout

3: Write Clear, Unambiguous Steps

Step:-1. Launch the client2. Call up a record3. Change the record but don’t save your changes yet4. Take the database server offline5. Attempt to save the record6. Receive a timeout error7. Exit the clientResult: Crash

1. Launch the client2. Query the database for new entries3. Launch a browser4. Read the news on yahoo.com5. Quit the browser6. Choose an entry7. Change the category from “vegetable” to “fruit”8. Take the database offline9. Attempt to save the record10. Receive a timeout error11. Exit the clientResult: Crash

4: Explain the Effectof the Bug, Not Just the

Symptoms

Examples:

1. A report that “an annoying dialog prevents you from closing application”

2. A report that “the application hangs on exit”

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)