This is not actualy a problem, but a paradigm shift. You've been told from day one when you started your professional testing career that you need specifications. And that is all you need. And then you found out that the literature said: specs should be correct, complete and umambiguous. And you thought: my specs are not like that. They are sometimes not correct, not complete, and

very ambiguous

. You spoke to your fellow testers and they said the same.

What you need to change, is the idea that documentation is all. In fact, in

any

project the documentation is not complete.

Documentation is just "a" source of information. If there isn't enough documentation, go ahead and get information. Use InformationAsASource.

Back to ContentTutorial