Is testing about checking against system requirements, or is it about exploring the software?

Sponsored Links:

Some time back Mr. Bolton published an article on testing vs checking. On same concept, Elisabeth Hendrickson wrote one asrticle Two sides of testing. I was reading an article on testing "Two sides of testing". Where Elisabeth Hendrickson answers Is testing about checking against system requirements, or is it about exploring the software? In her great article, there we couple of points she mentioned which are very note-worthy.

Elisabeth proves that following claim in red is not always true.

Many years ago in a hallway conversation at a conference, a test manager and I were discussing our respective approaches to testing.

 "If they can't tell me what the software is supposed to do, I can't test it," Francine, the test manager, scowled. "So, I tell them that I won't start testing until they produce a detailed requirements document."

My eyebrows shot up through my hairline. At the time, I was working for a Silicon Valley software vendor that made consumer applications. If I waited for a comprehensive specification before I started testing, I'd be waiting forever. And, I'd be fired for failing to contribute meaningfully to the project. I said something to that effect, and Francine just shook her head at me. She couldn't imagine not having detailed specifications. I couldn't imagine holding the project hostage until I got documentation.

Few more useful quotes:

In the past, I was firmly on the side of using exploratory approaches. For most of my career, I worked for organizations that preferred lightweight documentation, so we didn't usually produce detailed test scripts. Even if those organizations had wanted binders full of step-by-step test cases, I agreed with James Bach that sticking to a testing script is like playing a game of  Twenty Questions where you have to ask all the questions in advance.

However, my perspective on this debate has shifted in the past several years as I started working with agile teams that value testing in all forms. I have come to realize that the old discussion of whether "good testing" involves predefined, detailed test scripts or exploratory testing is like pitting salt against pepper, glue against staples, or belts against suspenders.

It is a false dilemma and a pointless debate.

So Guys, what do you think? Is testing about checking against system requirements, or is it about exploring the software? Give your comments below.

Click here to Read the complete article "The two sides of testing".