I’ve gotten to the point of believing that ISTQB is not just unhelpful, but actively harmful to the craft of testing.
I’m not a consultant or marketing anything. I’ve just interviewed a lot of candidates for both senior and entry-level testing roles and seen an astonishing general lack of critical thinking and creativity that I believe is in large part encouraged by this certification and the associated mindset that testing is about mindlessly churning out and executing test cases. It shouldn’t be the case that one can interview candidate after candidate claiming to have 10+ years of experience and yet their responses to very basic test design questions or hands-on testing exercises are generic, vague, shallow, and boring. It’s a disturbing trend and one that has made me generally favor hiring fresh college graduates because they are still full of creativity and curiosity, and haven’t been dumbed down by ISTQB and confirmatory mindset test practices.
Many of the arguments I hear (I’m not looking at a particular response, more of a “patterns over time” observation) in favor of people taking the exam don’t really hold water for me, so I’ll try to rebut a few of them here:
-
“It helps new testers get a foot in the door”: I think it encourages them to enter testing through the wrong door. One that emphasizes a confirmatory mindset and distracts from the critical thinking and creativity required behind a mountain of guff about “planning, managing, estimating, monitoring, and controlling”–not that any of these are necessarily intrinsically bad, but they’re treated as ends in themselves, versus means to and end, and encouraged to be process and paperwork-heavy, which necessarily takes away from actually testing.
-
“It’s necessary to get a foot in the door with job searches”: While it’s true that some companies likely require the certification, that’s a HUGE red flag for me that they don’t understand what good testing looks like, and I’d stay away from such companies. As for getting your resume past automated filters looking for keywords, simply putting something like “I have chosen not to pursue ISTQB certification and am happy to discuss why” on your resume would both satisfy an automated filter and demonstrate your knowledge and provide a more healthy conversation starter than a certificate.
-
“It provides a common language by defining a bunch of terms”: Sorry, I just haven’t seen it. I can’t say I’ve actually heard pretty much anyone who both demonstrates that they know what they’re talking about and also uses terms exactly the way the ISTQB syllabus does. But the harmful part is the flip side–people who have taken the certification and walk away thinking there is one “correct” way. The type where you present a vague, ambiguous problem that should obviously require asking a lot of questions to establish context to know what or how to test it and instead you get immediate, shallow “you need to do it this way” answers.
Bottom line, there are much better sources of information on pretty much anything useful to learn about testing than the ISTQB offers, with a lot fewer downsides. Some examples:
- BBST (Black Box Software Testing) courses
- Lessons Learned in Software Testing book by Kaner, Bach, and Pettichord
- Perfect Software, and Other Illusions about Testing book by Jerry Weinberg
- The Art of Software Testing book by Glen Myers
- Explore It! book by Elisabeth Hendrickson
- Learn Software Testing Course by Robert Sabourin and Dr. Lee Hawkins
- People to follow on LinkedIn and blogs (just to name a few):
- Michael Bolton
- Wayne Roseberry
- Brijesh Deb
- Richard Bradshaw
- Alan Richardson
- Angie Jones
- Bas Dijkstra
- Paul Grizzaffi