A bug is not in the application but it is in test script

The bug might have occured due to some errors in the test 
cases or due to some errors which occured during the 
execution of test cases.These can be the reasons for 
changing the status of a bug to not a bug.

Hi

A Test engg may Find it as a Bug, but after discussion with 
Test Lead it is consitered to be 'Not a Bug' status.

S.Ramprasad sun_ramprasad@yahoo.com

After getting the bug, we will be reporting the bug to the 
developer via Test Lead. Based on the discussion with 
developer and Test Lead, we can close the bug as " NOT A 
BUG ".

The wording will not be " NOT A BUG " rather after 
discussing u will be closing the bug under clarification 
for your further reference.

ALL THE BEST.....ARJUN(9440567637)

The reason for changing the status of a bug to ' NOT A BUG'
 might be:-
1.It might not be a bug but a feature in itself.Might 
happened that at a very late stage the programmer was 
intimated to introduce or change a feature i.e. there might 
be a spec change which was not well communicated to tester 
in time...so he considered it to be a bug.
2.Another reason may be that it be a testing error

a)	If the same build same bug is arises the two times 
then 1st bug developers put the status it is not bug.
b)	Because same bug already fixed and again coming the 
same bug so 1st is not bug that duplicate
c)	Other wise the developers fixed the two bugs he was 
done the two mistakes
d)	In weekly report lees then bug fix the that is good 
developers 
e)	So fixed the 1st bug is not bug.


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

In three situations we will change the status of a bug to
"Not A Bug".
1.Hold:- Whenever the developer is confused to accept or
reject its as a bug. Then he or she put its on a hold.

2.As per Design: Whenever the developer is done some changes
to the application, its were aware of test engineer and test
engineer raises its as bug and developer explains its was
done  as per design released latestly.

3.Tester Error: Whenever Developer's lead or Developer
confirms its as a tester error in findout the bug.

  In this scenario's the developer changes status as bug to
"Not a Bug".

“Not a bug” status arises when Tester misunderstood 
specifications and files bug according to his 
understandings.

"Not a Bug" status should be given to above mentioned "As 
per Design" situation, unless "By Design" status is 
provided.

In simple words, If you raise a bug which is "not a bug"