Hi



1.The Bug may not be reproducable at the developer end.
2.We will ask him to check the Business Logic or Business 
Scenario.

3. Finaly we will ask him to communicate with business
   alalyst to make a change in Business logic.
   when the Specification has been baselined after
   configeration we will close the bug.
   
   sun_ramprasad

I will show him the Client requirement Docuemnt i.e. SRS

A bug reported may not be a bug with the system developed. 
It may come from any supported third party product.

If developer does not agree with the bug/defect, he/she has 
to provide detailed clarification, why he/she is not 
feeling this could be a bug. All clarifications must be 
recorded in the bug tracking tool.
If tester finds a right justification and it complies with 
SRS, he could take right action for the bug.

if the dev does not agree it is not a bug ,then first we
will check whiah software & hardware used if both r same
then we will send some snapshorts & tracabulity matrix of
the corresponding bug ,even if he /she does not agree i will
report to tl.

Developer will have to post some comment on that bug in the
test management tool. If comment justifies the problem
sounds okay else the state of the bug will be reopen.

"I will show him the Client requirement Docuemnt i.e. SRS"

Developer also have right to see SRS. So no logic with above
statement. 



regards
kishore
kishoresharma05@gmail.com