tag:blogger.com,1999:blog-8951904624959546499.post8272837950043660933..comments2009-03-20T12:39:22.699-04:00Eric Jacobsonhttp://www.blogger.com/profile/08216361684596485033noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8951904624959546499.post-65501301212790611912009-03-20T06:33:00.000-04:002009-03-20T06:33:00.000-04:00I can so relate to your post !!!<BR/>I have a similar tester in my group who takes pride in helping developers fix their code when he is most wanted to find the remaining issues in the AUT.<BR/>He comes back and tells his fellow testers of how much he dig in to the code and fixed it ,while the dumb tester sitting with admiring eyes are the ones who have tested the application thoroughly.<BR/><BR/>Can u pls suggest some tips to deal with such testers?They are quite good,but how can we(testing Community) use thier goodness??Roshni Princenoreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-41456886340427046622009-02-28T09:15:00.000-05:002009-02-28T09:15:00.000-05:00So true. I've recently moved to the dark side of the force becoming a dev :) This means now I have to make sure my QA is fresh and not caught up in explanations why things don't work. Better yet, I've begun to slowly spread the awareness amongst devs not to accept things as they are, to admit it when things don't work.Ido Schachamnoreply@blogger.com