Testability of Requirements

If you are working on the Legacy and complex application and Requirement documents were not done earlier but the product emerges now.

How as a tester should understand the application before he runs the tests?

I know: Exploratory Testing is one of the ways. But it would be more time consuming if we are just wandering on the application.

Allow me to rephrase the question, just to be sure I’m understanding it correctly.

Assume that we have a project where some of the artifacts are either incomplete, missing or just plain wrong. How could we approach our testing in order to ensure that we are getting the most value out of our time?

Luckily for us, the artifacts, such as requirements documentation, are a very small part of the tester’s arsenal. The reference materials, can be missed, since we can still use inference, conference, and experience as oracles in order to understand our product.

This is a HUGE subject, so rather than explore it more deeply here, I will refer you to a set of blog posts which explain it much better than I ever could.

From Michael Bolton: https://www.developsense.com/blog/2015/09/oracles-from-the-inside-out/