I m new to testing..
I would like know how to track a defect and what are the ways of creating a bug report. Please excuse my sentence formations and terminology used if I m wrong. What I want to know is bout defect tracking and bug reporing..(elaborated)
We use a commercially available system from Mercury called Quality Center/TestDirector that works great for us. Currently we have over 51000 bugs logged into the database and stillgoing strong w/o scalability issues.
There are also many free defect tracking systems available such as Bugzilla and GNATS. I spoke to a guy working for the military who claimed that his department still used paper based defect tracking! Typical fields might be:
Steps To Reproduce...
There should be lots of info in these forums so have a search.
- Defect reporting: log what is important in your situation. What do you want to tell the people that must solve the problem? What do you still need to know when you will need to retest the solution? There are some general fields that are mostly applicable that you'll find on the web. But always evaluate what you really need. Reporting what you won't use is useless.
- Defect tracking: identify what statusses you want to know. Some companies want to know a lot of intermediate statusses. Others only want to know when they can retest.
All of the companies I worked had used PVCS Tracker. It is powerfull and flexible bug tracking system with support either web and system interfaces. It could be easilly integated for distributed projects, when developers, managers, customers and SW testers are separated geographically and connect each other by Internet.
As in any defect tracking (or bug reporting system) it will only be as good as the training on its use is. For example I have worked for companies that have use various defect tracking systems (anywhere from free to the afore mentioned PVCs Tracker) and the biggest complaint I see are users not using the system for its intended purpose. I have seen it used for Q&A’s, help desk issues even had a person send a request to a co worker to meet them for lunch. The other problem is with customizable systems and trying to over customize for a group. Defect tracking systems are basically a repository for issues and training the user to properly use the system is as important as what system you decide to use.
Just my 2cents worth
But in the end doesn't it all come down to BEER? Beer is the ultimate answer to all questions in the universe so yes the answer to your question is BEER.