Write papers in time

So,

All from us works with docs, requirements, specifications, plans, test suites and other project support information. And we are happy to read them and use for testing and analyzing usability. A major value, I suppose, which you should parse from that waste papers - applicability. 

But, sometimes when projects starts there is no any from that docs. In this case the docs will be created in future, maybe,.. if stars will gets on. So, we have the one simple problem - how should we test? Launch app from global repo, or install app on device and start Ad-hoc testing and find unknown pages artifacts, bugs,.. or features (?). Simple way. And if we use quick increasing application, with a lot of short milestones, big developers team, - there is other circumstances. And we still have no any project documentation. 

What note a bug-report should be based on?

Project documentation is used - always. For customer`s preview, simple demo, production presentation. It is necessary condition for all these events!

I have chosen a way, when when project documentation is writes in the first steps of feature testing, when you begin to work with new functionality. You just spent a day for making screens and creating short presentation like "how to " or "manual", set up test cases, and go on. You can talk with developers with unquestionable facts in debates, that they done a mistake or this feature has an other different behavior some builds later. 

Second useful feature of this way is that you can test your app without thoughts, that you is need to write it for Friday`s meeting. Otherwise, you have this note in your had every day from Monday to Friday morning. And on Friday morning you exactly write this paper and test the application, track bugs and debate with devs, as usually happened. And in the evening you have square head red eyes and will ask yourself -"What the fu**ing Friday has happened?".