Can you fix that issue now? :-)

1

Posted by Amit Kulkarni [Admin] | Posted in , , , , , , | Posted on 12/04/2009 09:59:00 PM

How many times this happens with us (testers)? The issues reported by you - get rejected or closed saying that the user will not try such weird thing. I believe this is a part of every testers' life. Correct me if I'm wrong!


This story happened quite a time back, not so long though. I reported one issue - reported and assigned the issue to the developer working on that project. As per the practice sent out email too to make sure that everyones is aware of it. Few days passed by like this as there were some other issues too. I'm being assigned back the issues fixed by the developer, so I had to perform regression testing. One morning I just came to the office - such a fine day (because it was Friday) so I was more happy. :-) I checked my mail and surprised to see that the developer has re-assigned the issue to me the one reported earlier. The developer asked me to close the issue - Reason: "User will not try such a scenario, so can you please close this issue. Thanks". I thought I should talk to the developer for the last time to make sure that - this is what it meant. I went to him and queried about it and found that he meant the same. After discussing the same with TM,PM and concerned developer - I decided to close the issue. 


Months passed by and the project was successfully deployed. Everyones' happy. ;-) 


Everyone busy in their work and just working on the other project. The one fine day we got an email which was forwarded to us by our PM - says that the issue # xxxx need to be fixed on PRIORITY. Meeting has been called for the same by PM. We went to the meeting rooms (not to mention carrying out pad/pen with us) and found out that the discussion was getting heat up. After a good analysis in our Bug Tracking tool we found that I closed the issue but not to mention that, notes section contains the reason the developer has given to me. They questioned me and I answered back that this is the same issue that I closed for the reason given by developer. I was safe as all the time everyone aware of this. Then PM started saying that one user has indeed tried the scenario mentioned by me in my report and there is an issue now. This is the users' response and now the customer has asked us to FIX it. Meeting ended with discussing the things like fixing of the issue on PRIORITY, time spent, time for testing, what needs to be done on PROD and analysis report which needs to be submitted by TM


After coming from the meeting room I went to developers' desk [not to mention big smile on my face :-)]....just asked him:


Can you please fix the issue now? :-))


Best Regards,


Amit


testing is my passion!!!
http://bugteaser.blogspot.com 


Started writing the blog: 9:20 PM and completed the blog: 09:59 PM

Reactions: 

Comment (1)

Yes Amit.. You're absolutely correct.. Even I have faced the same problem, but that was my first and last. Afterwards I never used to close/ignore a bug until my manager's approval.