Save 37% off PRO during our Black Friday Sale! »

Software Testing Quotes

Software Testing Quotes

You can let all the different types of testing scare you out of your pants or you can look at the funny side of testing. These quotes could be a starting point...


Nick Parfene

April 23, 2015


  1. • Installation testing • Compatibility testing • Smoke and sanity

    testing • Regression testing • Acceptance testing • Alpha testing • Beta testing • Functional vs non-functional testing • Destructive testing • Software performance testing • Usability testing • Accessibility testing • Security testing • Internationalization and localization • Development testing • A/B testing • Concurrent testing • Conformance testing or type testing Testing is a complicated beast. But it can also be fun
  2. The starting point for improvement is to recognize the need.

  3. Focus on lower costs often leads to lower quality. Focus

    on higher quality always leads to lower costs.
  4. A relatively small number of causes will typically produce a

    large majority of the problems or defects.
  5. Always code as if the guy who ends up maintaining

    your code will be a violent psychopath who knows where you live. Martin Golding
  6. A program which does not work is undoubtedly wrong, but

    a program which does work is not necessarily right.
  7. Programming is like sex: a single mistake leads to providing

    support for a lifetime.
  8. All code is guilty, until proven innocent.

  9. If debugging is the process of removing bugs, then programming

    must be the process of putting them in. Edsger Dijkstra
  10. Software and cathedrals are much the same: first we build

    them, then we pray.
  11. Absence of evidence is not evidence of absence.

  12. Debugging is twice as hard as writing the code in

    the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. Brian W. Kernighan
  13. Everything human is at least a little bit broken.

  14. Testing is organised skepticism.

  15. Trying to improve software quality by increasing the amount of

    testing is like trying to lose weight by weighing yourself more often.
  16. 3 Biggest Software Lies: •The program’s fully tested and bug-free

    •We’re working on the documentation •Of course we can modify it
  17. Quality means to also do things right when no one

    is looking.
  18. Where is the ‘any’ key?” (Homer Simpson, trying to figure

    out the “Press any key” notification)
  19. Quality represents the wise choice of many alternatives.

  20. When debugging, novices insert corrective code; experts remove defective code.

    Richard Pattis
  21. If you don’t like testing your product, most likely your

    customers won’t like to test it either.
  22. Quality is remembered long after the price is forgotten.

  23. Program testing can be a very effective way to show

    the presence of bugs, but is hopelessly inadequate for showing their absence. Edsger Dijkstra
  24. Software testing is the art of trying to increase confidence

    in a product by pointing out everything that is wrong with it.
  25. f u cn rd ths, u cn gt a gd

    jb n sftwr tstng.
  26. If automation processes had been flawless, they would have been

    called "automagic".
  27. With good program architecture debugging is a breeze, because bugs

    will be where they should be. David May
  28. The bitterness of poor quality remains long after the sweetness

    of meeting the schedule has been forgotten.
  29. Fundamentally you can’t do your own QA, it’s a question

    of seeing you own blind spots.
  30. Software testers do not make software; they only make them

  31. If you automate a mess, you get an automated mess.

  32. The trouble with programmers is that you can never tell

    what a programmer is doing until it’s too late. Seymour Cray
  33. Fast, good, cheap: pick any two.

  34. If you don’t care about quality, you can meet any

    other requirement.
  35. One of my most productive days was throwing away 1000

    lines of code.
  36. Measuring programming progress by lines of code is like measuring

    aircraft building progress by weight.
  37. If you don’t care about quality, you can meet any

  38. Bad programmers have all the answers. Good testers have all

    the questions.
  39. Why do we never have time to do it right,

    but always have time to do it over? Murphy’s Law
  40. Alpha is simply that you want somebody to share your