Interested to Buy Any Domain ? << Click Here >> for more details...
What might be the reasons for changing the status of a bug
to " NOT A BUG " ?
- 13 Answers
- 20202 Views
- Accenture, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / m.srikanth
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".
| Is This Answer Correct ? | 5 Yes | 0 No |
Answer / hari
“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.
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / amit verma
There may be several reason for the status of a bug to '
NOT A BUG' are as follows:-
-Change in Requirement or Design,Developers can set the
Status as " NOT A BUG".
-If the bug is not Reproducible again then Status of the
defetc is set as " NOT A BUG".
-Sometimes Invalid bug marked as " NOT A BUG" also.
-Lack of understanding either Developer side or Tester side.
Let me Know if i m wrong!!!!
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / vineetbatham
if tester report any bug and developer open it.
1. developer fails in replicate the same scenario. and
tester also fails to re-generate the scenario in which the
bug was found. It is not a bug (Rejected)
2. If test lead & team getting a satisfactory reply from
the development lead & team, the test lead marks the bug as
rejected.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / karunakar reddy
If Defect Is Raised Due to lack of SW or HW or Alreday
Raised Defect or Due to Mistakes In Test case Then Developer
Will Deside That Is Not BUG.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / mudaseer
if test engineer misunderstands the requirement ie he thinks it as a bug but developer has developed according to requirement the status of bug is changed to not a bug.for example i had sent a bug to gmail.com the bug was i had saved some data in draft and i sent the data to my friend so the data was in sent items but it was not there in draft so i thought it should exist in drafts also so i prepared a report and send it to gmail but i discussed with my friends about the
bug i sent they told u have misunderstood the functionality.so the bug status was rejected
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / vijayta
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
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / k.chandra sekhar
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
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / arjun reddy.n
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)
| Is This Answer Correct ? | 0 Yes | 2 No |
Answer / mythily jasthi
In simple words, If you raise a bug which is "not a bug"
| Is This Answer Correct ? | 0 Yes | 2 No |
Smoke testing is ------ 1.sanity testing 2.Functional Testing 3.Build Verification Testing 4.Regreesion Testing
What is defect masking?
on what basis a tester writes test cases,i mean is it only based on FS and if so how can they know that a certain no of test cases can be written even b4 they write the test cases.bcoz a test plan contains how many test cases to be written by each tester.
Work flow in testing in your company?
What are noise variables?
Hi, this is sekhar yadav plz answer my questions with(examples) highest seviarity &lowest priarity and lowest seviarity & highest priarity ???? i want proper answer .. thankq
hai, pls. explain V-Model clearly. Pls. give me guidience how to explain V-Model in interviews?
How to explain the project? (banking)
what is test case ,,,real time i want defination pls ,pls
Do we have any certifications for ETL Testing ?
differentiate re-testing and regression testing
Hi frnds im mini. can any one give correct answers for this interview questions. i have an interview in 4days..pls 1.What are tests that u have participated in Testing. 2.What is diff between Load testing Stress testing? 3.What is sanity testing when do u start it? 4.how can you test ur application with negative testing? 5.when can u start test case writng? 6.what is the tool your are using and the version? 7.what is the tool you used to report the bug ? 8.what is a formate of test case document in your company and also bug report document formate? pls send me reply.. tank u frnds.............
Automation Testing 
