Quality Assurance and Project Management

Mar 5 2014   8:07AM GMT

A Good Programmer Cannot be a Good Tester To Replace One

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

It has become as well proven fact that a tester cannot become a good programmer and a programmer cannot be a good tester. It does not mean that a programmer doesn’t know how to test or he doesn’t have the capability to test the code he has written but testing his code as a tester is not possible for a programmer. There are various reasons given on the reason that why a good programmer is not a good tester in one of the earlier posts. One of the main reason is that a writer cannot be a critic of his own writing. Same goes true for a programmer. Programmer loves what he writes and himself would not love to find out fault in what he has created.

Even when there is a testing done by a programmer/ developer after writing his code, the prime thing in his mind remains that the code has been created by him and that is what holds him going into customer’s shoe and looking at the code from customer’s perspective. Whatever a programmer tests in his code is the technicality of the code. Two important things that he misses to map with his code are – one, the business flow; and two, the usability. At many instances I have discussion with developers on what they have written and what business requirement had been. And on such instances most of them argue to accept it as per the code written and express reservations in changing the code as per business requirement, by giving different reasons.

2  Comments on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • rebeccajoyB
    I agree. Everybody is unique. So, he can't replace anyone.
    10 pointsBadges:
    report
  • CharlieBrowne

    I agree.

    It is two different mindsets.

    The programmer tests to prove his code is working.

    The QA person tests to prove he can break it.

    41,430 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: