Hi All... [img]images/icons/smile.gif[/img]
Currently I am following the following format...
in manual testing
Standard TC fields + Bug report fields.
I need help in the bug report format.
Currently the format I use is...
Bug Status 1 (When QA finds the bug)
Bug Status 2 (When dev. fixes the bug)
I am confused with the Severity and Priority fields as well as the overall format.
I as QA assign the severity. Do I assign the priority ? or the developer assigns it ?.
Can anyone give me a more better bug report format?...and clear my confusion. [img]images/icons/confused.gif[/img]
thanks in advance...
Generally Severity of the bug is assigned by the tester who has found the bug based upon how severe the bug is like Showstopper/Major/Minor
In Majority of the cases, Project Manager would take the decision as when is the appropriate time for fixing the bug and assigns the priority.
The decision of assigning a priority again would be made on several conditions like
1) impact of the bug on functionality
2) time available for fixing the bug for the current release
3) feedback from client as how important is this bug being fixed for him?
In our case the priority is set by the Development and QA managers, and approved or disapproved by the Change Control Board. You as a tester, would normally not be responsible for setting priority.
Success is the ability to go from one failure to another with no loss of enthusiasm.
~ Winston Churchill ~ ...Rich Wagner
Similiar to Rich, but different, it is our release manager and business sponsor who decide the priority, not test, in my current context.
Agile Testers of the World UNIT!
For more contextual Musings visit http://www.testingreflections.com/ and now at http://www.sqablogs.com/neillmccarthy/
I would suggest that some browsing/searching of the Defect Tracking forum here at QAForums might be in order.
web site | [url=http://www.ebookworm.us/[/url]
[i]...Sound trumpets! Every trumpet in the host! / Sixty thousand, on these words, sound, so high the mountains sound, and the valleys resound.</i] (The Song of Roland)
I would recommend that a test case reference number also be added to your defect report so that your development team can easily see your "steps to recreate" the defect.
I am fully convinced by srinivas. He has explained you in detail. I suggest you follow his directions.
I too agree with Srinivas.
In my company, it is the tester himself who assigns the severity and priority for the bug, but the test lead can modify the priority before assigning the bug to be fixed.