vk1978

 Profile Answers by vk1978 Questions by vk1978

• Mar 22nd, 2009

 

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.

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Mar 23rd, 2009

 

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...

vk1978

 Profile Answers by vk1978 Questions by vk1978

• Mar 23rd, 2009

 

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

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Mar 24th, 2009

 

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.

vk1978

 Profile Answers by vk1978 Questions by vk1978

• Apr 17th, 2009

 

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

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Jul 23rd, 2009

 

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

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 5th, 2009

 

In every test cycle, the defect is consistently 'Ignored' by the developer and 'Re-Opened' by the tester.  This problem exists due to a miscommunication somewhere.  What will you do as a tester to rectify this issue?

1) I would first make sure that I have entered accurate and thorough details in the defect report in order for the developer to reproduce the issue. I would include details about the test environment so the developer can duplicate it.  I would also include screen shots to prove the defect does indeed exist. 

If the developer 'Ignores' this, then s/he obviously believes there is no defect at all and that the application's functionality is working precisely as it is supposed to.
 

2) Next, I would cite the requirement in the defect report and describe my interpretation of it.  Then I would describe how the existing functionality does not meet the intended requirement.

If the developer 'Ignores' this as well, then I begin to consider whether I have misinterpreted the requirement. It is possible that the developer is correct.

3) I would revisit and study the requirement to determine whether I misunderstood it when creating my test case(s).  If necessary, I would meet with the Business Analyst to gain further understanding about the requirement.  I would discuss my test case and the defect with the Business Analyst to determine whether my understanding and approach is correct.
 
If my research convinces me that I have fully understood the requirement and that my test case accurately and thoroughly tests it, then I would meet with the developer and discuss the results of my investigation with him/her.  I would explain the requirement in the manner intended by the Business Analyst.  I would reproduce

the issue in an attempt to prove how the defect fails to satisfy the requirement.  Hopefully, the developer will be encouraged to fix the defect.

If the developer continues to 'Ignore' this issue, then I will get the Business Analyst involved.

4) I would set up a meeting with the developer, Business Analyst, and myself in attendance.  I would encourage the Business Analyst to explain the requirement to the developer and explain how the test case and its results properly exercise the requirement and identify a failure. 

If the developer still 'ignores' this issue, perhaps it is time to replace the developer!

folasade

 Profile Answers by folasade 

• Feb 18th, 2010

 

If a developer is fixing bugs with their own ideas and schedule in mind that means he is not following the test cases, he changing the status to IGNORED, then it is an error on the part of the developer who is not following the standards and not working as part of a team. As the owner of the defect we testers are responsible and need to close the defect, we need to ensure that the developer fixes that issue as the defect has been IGNORED on multiple builds. To do that we need to sit with the developer and explain the requirement as it seems that he is not clear about the requirement or the severity of the bug and try to reproduce the defect in front of developer this will also display to him the impact of that defect, seeing is believing!

venkatesh.thangaraj

 Profile Answers by venkatesh.thangaraj 

• Sep 14th, 2010

 

To be very simple, tester should specify the functional document(FD) which tells the exact functionaly of the piece of code and explains how it deviate from the requirement which lead to a creation of bug.
 
Also a tester should replicate the bug in the development environment along with the concern developer who ignores the bug and to make him to accept the bug for fixing it going further.