Interested to Buy Any Domain ? << Click Here >> for more details...
Can anybody describe what might be the reasons or situations
where the developer doesn't accept a bug as a bug , raised
by tester ?
- 13 Answers
- 18784 Views
- Accenture, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
>Defect may not reproducible
>Environmental issues
>Not specified in requirements
>Defects related to GUI which are frequently changing developer might not able to see or identify becoz of ur insufficient description.
I think th
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / k.chandra sekhar
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
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / deepak
> When it works on developer machine
> When there is a functional workaround to the issue
> When bug is related to something specific in nature (like
perfomance failure) and the saem characteristics was not
specified in Requirements specs to cater for
Other more interesting factors:
> Developer is frustrated because of no salary hike
> Developer is irritated by tester
> Developer has to fix an issue in module written by other
developer
Anyways, Mr. K Chandra's answers are I guess best (if can
be understood)
| Is This Answer Correct ? | 2 Yes | 1 No |
Answer / senna
The most common scenario is when the developer cannot reproduce the issue in his or her system. Another frequent scenario would be when the developer deems the issue as working as intended and now it is up to the tester in conjunction with the test lead and BA to prove it is not. A slightly less common scenario is when there already exists a similar open defect and in this case the newer defect would be marked as duplicate and rejected.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / divya rana
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.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / dfivya
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
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / hari
1. When the Bug is not reproducible at Developer's End
2. Misinterpretation
3. Environmental issues
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / tentativenights
Guys plz suggest proper solution to the problem. My project
manager is not satisfied with thees answers.
So plz reply as soon as possible
Thank you !!!
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / mohammed iliyas
Yes, i had lot of situation on this case. Developer is not agreed the bug which we raised.
When we raise a defect, we need to understand the case where the functionality is failed. Sometime we raised bug, But this is not a bug due to some other logic in the application for which this case is work fine.
and if is failed due to some other logic, then we should have to clearly explain the what exactly the case. Then only developer will agree.
And the above case we come to know only when developer is given the justification(after reviewing the entire code)
| Is This Answer Correct ? | 0 Yes | 0 No |
There is an opening in our organization Sierra Atlantic, Hyderabad. All Manual test engineers with 2-3 years or experience can forward your resumes to mah_cs82@yahoo.com before May 01, 2008. (Only manual testers)
What is bug, deffect, issue, error?
wht is IEEE 829
Define Non-functional testing?
How do we test the requirements?
What does scalability mean. Is the system scalable only in terms of hardware or its software which makes the application scalable. Please provide an example to support your answer.
What a team leader will test first when s/he will get new module to test?
When the GUI Testing will be held on the V model ?
difference b/w test case doc & use case doc?
what is the format of traceability matrix?
Differentiate Defect age and Build interval.
Difference between Test scenario and test cases?
Automation Testing 
