Testing with less requirements

Never experienced the saying assumption is mother of all, but my last week's testing approach gave a chance to experience it…. might be my preconceived notion about testing never allowed me to know about it

A gist of what I have learned last week…

I was directed to test an unfamiliar application which has very less or no requirements, I felt as if I was asked to chart a course through unknown waters, cause all my testing skills and approach are limited to testing applications which has requirements or either well documented...

But I was wrong;

I learned one of the greatest lessons that lack of thorough requirements helps testers to exercise the art of creativity in attacking the software for defects and vulnerabilities… Applications which has very less requirements can be defined with a set of boundaries and direction– informing testers what is “in scope” or “out of scope”, usability concerns and what the goals are

To wrap up

Completeness of testing a product entirely depends upon the perspective and the context.one doesn’t always need to wait for entire requirements to test a product… more important is “Software testers need to be agile enough to test both in planned and free testing environments “

I learned one of the best testing approach -- Exploratory testing thanks to michael bolton and james bach