I would much rather test than create test documents. Adam White once told me, “If you’re not operating the product, you’re not testing”.
It’s soooooo easy to skip all documentation and dive right in to the testing. It normally results in productive testing and nobody misses the documents. Until…three years later, when the prog makes a little change to a module that hasn’t been tested since. The team says the change is high risk and asks you which tests you executed three year ago and how long it took.
Fair questions. I think we, as testers, should be able to answer. Even the most minimal test documentation (e.g., test fragments written in notepad) should be able to answer those questions.
If we can’t answer relatively quickly, we may want to consider recording better test documentation.