if the tester raised bug is not reproducible in development
environment

tester does not providing any strong reasons to accept that 




i think these are the strong reasons i think

correct me if am wrong

thnks and bye
subhan.k

If a bug is an "inconsistent bug",there could be high 
chances of the developer denying to accept a bug as bug
                    or

If the software being tested has certain pre-requisites 
regarding the environment where it is to be run/executed 
and the environment in which the tester is testing that 
software is not matching,then the application under test 
might give some some incorrect results which the tester may 
consider it as a bug but developer may deny that.
                       or

If the front end  where the user is supposed to enter the 
data is coded such that the length of the datafields is not 
compatible with those that can be supported in the 
database's coding ,then it could so happen that when tester 
is trying to enter the data in the textfields ,system might 
apparently accept it and save it but next time when the  
tester tries to view the saved data after refreshing it,he 
might get to see incomplete data which he might report it 
as a bug but the developer might justify that it is not a 
bug,the length of textfield is different from the database 
which the tester needs to explore that what is the length 
of the those textfields.

In the above answer,third situation is the one where if 
such a case happens where the front end field's length is 
not compatible with the database's coding,then it is very 
much a bug which the developer should accept and rectify it.

a)	If the tester only send the defect format then 
easily not excepted developers
b)	 If the developers accepted that type of defect 
then developers loss the his confidence to the team members
c)	So the tester with the defect snapshots, tester 
environment and his approach the total description sends 
then the developers check the description then accepted.


My name is k.chandra sekhar,
My phone no is 09246540049,
Hyderabad.
My mail id is ndra_143@yahoo.co.in 
If any body want full explain send that mail

I am sorry Mr.K.chandra here he is asking, at what 
situaation sthe test engineers defeect not accepted by the 
dev. wat the ans given by u is the steps to b followed for 
the nonreprodusable deffects.

And one more thing,Mr.Subhan.qa, we cant say the defeect as 
the Bug until the dev fix that.so trat a defeect as bug.
The rejected deffect may be fix later then we can say that 
as Bug.

The main reason for rejecting the defeect is "non 
reproducablility of the bug and Environment difference 
situations>
k, thanq, Guys,
pls correct me if i am wrong

1. When the Bug is not reproducible at Developer's End
2. Misinterpretation
3. Environmental issues

K.Chandra Shekar....plzzzz I request you to first learn the
concepts well and as well as English grammer.....after tht u
can post it on this site.....

Once the tester raises an issue,he should be strong enough 
to prove that it is a bug by giving strong points and 
explaination.He should be aggressive of what he said.
when his points are not valid,there may be a chance that 
developer can reject it..