Posts Tagged ‘cliché’

Testing Clichés Part V: Testing needs a test coverage model Rikard Edgren 16 Comments

I believe there is too much focus on test coverage , there is even an axiom about the need of it. My reason is that no coverage model captures what is important. Cem Kaner lists 101 possible coverage models (Software Negligence and Testing Coverage), and none of them are super-good to me (my favorite is […]

Testing Clichés Part IV – We can’t find all (important) bugs Rikard Edgren 4 Comments

It’s a truth that we can’t find all bugs, but is it really a truth that we can’t find all important bugs? And it’s a cliche when used as answer to the (sincere) “why didn’t you find that bug?” question. Testers are paid to find important information about what they are testing, and included are […]

Testing Clichés Part III: “We can’t test those requirements” Rikard Edgren 12 Comments

It is good to strive for better requirements by critical analysis (and looking for what’s missing), but there is a danger in complaining about untestable requirements. If those vague requirements are changed (made too specific) or removed, the words in the requirements document have less meaning, and less chance of guiding towards great software. And […]

Testing Clichés Part II – Testing should be separate from development Rikard Edgren 5 Comments

This is an idea you see and hear now and then. It comes in different shapes, ranging from testers needing to have an independent manager, to testers being best if physically separated from developers, or even outsourced, or crowdsourced. Cem Kaner writes in The Ongoing Revolution in Software Testing that this notion primarily is a […]

Testing Clichés Part I – Expected Results Rikard Edgren 3 Comments

Sometimes it is said that each test case must have an expected result, or even worse, that each step of a test case must have an expected result. This is the extreme of scripted testing that I dislike for two reasons: * It takes a lot of time to write and follow detailed test cases; […]