Active Topics Memberlist Calendar Search Help | |
Register Login |
One Stop Testing Forum : Types Of Software Testing @ OneStopTesting : Automated Testing @ OneStopTesting |
Topic: How is a defect reported? |
|
Author | Message |
tanushree
Senior Member Joined: 04Apr2007 Online Status: Offline Posts: 2160 |
Topic: How is a defect reported? Posted: 26Oct2007 at 4:28am |
How is a defect reported? Once the test cases are developed using the appropriate techniques, they are executed which is when the bugs occur. It is very important that these bugs be reported as soon as possible because, the earlier you report a bug, the more time remains in the schedule to get it fixed. Simple example is that you report a wrong functionality documented in the Help file a few months before the product release, the chances that it will be fixed are very high. If you report the same bug few hours before the release, the odds are that it wont be fixed. The bug is still the same though you report it few months or few hours before the release, but what matters is the time. It is not just enough to find the bugs; these should also be reported/communicated clearly and efficiently, not to mention the number of people who will be reading the defect. Defect tracking tools (also known as bug tracking tools, issue tracking tools or problem trackers) greatly aid the testers in reporting and tracking the bugs found in software applications. They provide a means of consolidating a key element of project information in one place. Project managers can then see which bugs have been fixed, which are outstanding and how long it is taking to fix defects. Senior management can use reports to understand the state of the development process. Post Resume: Click here to Upload your Resume & Apply for Jobs |
|
IP Logged | |
zephyr
Newbie Joined: 26Dec2007 Online Status: Offline Posts: 1 |
Posted: 05May2008 at 3:11am |
Defect reports are probably primary work product for most of the
software testers. Good bug report, which is informative and
understandable earns you a good reputation. Weak report generate extra
work for everyone. Most of the time, a weak bug report is returned with
comments saying not clear, need more information etc. That makes you
work again on the same defect and thus reduces efficiency of testers
and developers both. Defect reports are not only used by programmers,
but also by managers, executives, documentation team and support
executives for various reasons.
Although there are many tools available I would suggest that you try Zephyr, a comprehensive Test Management System with a sharp Defect Tracking feature. It's graphical and very effective in finding, reporting, retesting, verifying and closing defects.
|
|
IP Logged | |
rahul.in.reddy
Newbie Joined: 10Sep2008 Location: India Online Status: Offline Posts: 1 |
Posted: 10Sep2008 at 10:52am |
Once the defect is find, The defect will be sent to either development team or to QM through defect tracking tool. Ex : Bugzilla , QC , TD etc
|
|
RAHUL REDDY
|
|
IP Logged | |
Forum Jump |
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
© Vyom Technosoft Pvt. Ltd. All Rights Reserved.