Test Notes

I don't make software; I make it better
  Home  |   Contact  |   Syndication    |   Login
  68 Posts | 0 Stories | 22 Comments | 641 Trackbacks

News

  

Please Note
The information in this weblog is provided “AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion.


Google Groups
SoftwareTesting
Browse Archives at
groups.google.com



  Page Loads:

Technorati Profile

Click for Hyderabad, India Forecast

Archives

Post Categories

Image Galleries

Friend's Blog's

Groups

Sites

Testing Blog's

Repro This!

A tester finds and logs a bug. Some days (weeks (months)) later a developer picks up the bug and runs through it. The bug does not occur. What should the developer do with this bug?  We faced this type of issues several times.  Using incremental build process this type of situation usually comes.  What will be answer of the question “What should the developer do with this bug???”  Go on and read the most common answer, less common answer and extremely rare answer for this question @ http://blogs.msdn.com/micahel/archive/2004/12/08/278330.aspx

posted on Friday, December 10, 2004 2:15 PM

Feedback

# re: Repro This! 3/2/2005 3:00 PM Neeru
I guess that kind of bug should be marked as FI (Fixed Indirectly) and tester should provide relevent comments before closing this bug

# re: Repro This! 6/14/2005 4:50 PM Vinoo
Rather than putting it as FI(Fixed Indirectly) why not put it as Fixed. The bug is anyhow fixed directly or indirectly and reproducing is not possible.
I feel the most rare answer given by the author in the link is a nice one if the developer and the tester debate on the bug. Even I personally came across such embarassing situation when the developer changed the bug which i have reported previously as 'Not Repro'.
1st thing - the effort put to find the bug goes invain
2nd thing - The healthy relationship between the tester and the developer disturbs



# re: Repro This! 2/28/2006 10:32 AM arjun
If it is a incremental build ,then the bug should be first regresssed on the build it was reported first.Although it might be fixed there is no guarantee that the bug is fixed just because it is not reproducable.

There is every chance that it is not showing up due some changes in that part of the code.Guess that is where regression comes in.

I have heard this more often now :CNR.That is totally unacceptable according to me

Post Feedback

Title:
Name:
Email: (never displayed)
Url:
Comments: 
Please add 6 and 6 and type the answer here: