Discussion - Mis-Communication in Bug

GeekInterview.com > Interview Questions > Testing > Discussion

Go To First | Previous Question | Next Question

Discussion | Question 69 of 72

Mis-Communication in Bug

What will you (Tester) do if there is miscommunication in bugs, Every cycle is Ignored from developer side and Re-Opened from tester Side?

Total Answers and Comments: 6

Last Update: July 23, 2009 Asked by: mathan_vel

Sponsored Links

Best Rated Answer

—

Submitted by: vk1978

if developer is executing test cases with their own ideas mean he is not follwoing the test cases(i mean steps to reproduce), and if he is not following and not understanding means he is not insync with the test cases and or requirement and therefore he changing the status to IGNORED

Then it is the mistake of developer who is not following the standards.

but as the Owner of the defect we testers need to close the defect for the sake we need to force the developer to fix that issue as the defect is IGNORED in Multible builds.

To do that we need to sit with the developer and explain the requirement first as he is not clear about the requirement and next we have to explain the deviation and try to reproduce the defect in front of developer and also will explain him the impact of that defect

that how we can handle

Above answer was rated as good by the following members:
mathan_vel

March 22, 2009 21:45:18

vk1978

Member Since: February 2009 Contribution: 174

RE: Mis-Communication in Bug

Let me start with what I understood with this question a defect/bug that is
opened by tester to which development team has not handled since 1 or more
builds and is not rejected by developer because of duplicate or differed.

If I am correct The defect might be a low priority one due to which
developer is giving less importance to fix because of fixing the high priority
defects.

If the defect is a high priority one even then development team is ignoring
it then what generally as a tester whatever defect I have raised I have to
make sure that it is fixed in the coming builds and more over in weekly team
meetings I need to give the status like how many defects are still in Open state
and what is the reason behind why they are not yet fixed if they are not fixed
since 2 or more builds so for these kind of defects I need to contact concerned
developer and inform him that it is not yet fixed since so and so builds and
explain the impact of that defect due to which other areas are not covering
while testing and request him to fix it as soon as possible.

If still he is not handling the issues then the issues will be raised by the
team lead with the high level management in their day to day meetings and
forcing the development team to fix the issue that s how we can handle the
things.

Plz correct me if I am wrong

And one more thing in your question you have mentioned Re-opened from tester
side could you give more clarification on this . I am asking this question is
because you said development team is Ignored the defect if it is correct then why
do we reopen the defect.

Is this answer useful? Yes | No

March 23, 2009 06:52:47

mathan_vel

Member Since: December 2007 Contribution: 422

RE: Mis-Communication in Bug

Dear vk1978
During retest also tester found that the issue is not closed. so he/she has put the status as 'Re-opened' the developers again put the status as 'Ignored' coz of miscommunication...

Is this answer useful? Yes | No

March 23, 2009 14:36:28

vk1978

Member Since: February 2009 Contribution: 174

RE: Mis-Communication in Bug

Developer has changed the status From Open/Re-open to Ignored due to Miscommunication what do you mean by Miscommunication is it with respect to Test case or steps to reproduce or expected value or any other thing?

thanks
vk

Is this answer useful? Yes | No

March 24, 2009 02:57:31

mathan_vel

Member Since: December 2007 Contribution: 422

RE: Mis-Communication in Bug

Let me explain with example

Tester founds a Bug and generated in the bug report with status as new and opened by TL.

Test Cycle 1:
Developers execute the Test Case bug with their own ideas and not understand and mentioned the status as "Ignored"

while retest Tester(s) execute the Test case bug and again noticed that the same bug is still there and mentioend the status as "Re-Opened"

My Question is in what ways the Tester can make proof on the bug is there still and how they can intimate clearly to developers for this opened bug.

Is this answer useful? Yes | No

April 17, 2009 01:21:35

vk1978

Member Since: February 2009 Contribution: 174

RE: Mis-Communication in Bug

if developer is executing test cases with their own ideas mean he is not follwoing the test cases(i mean steps to reproduce) and if he is not following and not understanding means he is not insync with the test cases and or requirement and therefore he changing the status to IGNORED

Then it is the mistake of developer who is not following the standards.

but as the Owner of the defect we testers need to close the defect for the sake we need to force the developer to fix that issue as the defect is IGNORED in Multible builds.

that how we can handle

Is this answer useful? Yes | No

1 0

Overall Rating: +1

July 23, 2009 08:09:12

srinivasulub1981

Member Since: December 2005 Contribution: 381

RE: Mis-Communication in Bug

Hi

Mis communication will happen due to so many reasons like below

-> Dev Didn't executed proper tcs though tester given proper test steps
-> May be dev using another environment for ex: tester found the issue in firefox
dev using in IE
-> May be the issue is not a reproduceble one
-> Giving Proper data may be failed.
...................................................................

Testers Activity:

-> If it's going on then consult the dev if both are in same plance and disucuss about

the issue i think most of the issues will rectify here.

Srinivas

Is this answer useful? Yes | No

Go To Top

User Name		Remember Me?
Password

Question Bank