When you're reporting on test status (verbally or written), be sure you establish a relationship between your testing and your mission. The following questions can sometimes help with that:

• Was I successful?


• Am I finished?


• What obstacles do I have?

Bug reports need to point out what the issue is. If the issue isn't obvious, add a note to the bug report stating what the issue is. Or state what you expect to see changed.

Most defect management tools are configurable to send you an email when events occur on tickets in your queue. Sometimes, this can get annoying, and many times people I work with direct those messages to a folder and never look at them. Instead, try using an RSS feed from the tool. Example tools that supply RSS include JIRA, Bugzilla, and FogBugz.

Depending on the tools you use, you might consider attaching automated scripts to your defects. If you can find a bug, and then quickly record a simple script that recreates it, attach that and send it along with the defect report. Dave Christiansen has done this using Selenium with much success.

If at possible include the build number on screen shots captured and added to bug reports. Also, if testing a web app, get the URL into the screen shot.