How to write a Test Teadiness Plan and Report
I have just started a new role as a software tester test bespoke software created for a client. The client is insistent that they want to see a Test readiness plan and report prior to the deployment of the software into UAT.
I am only aware of a Test Summary and Report please any advise on how to write this will be appreciated.
Better still a template if available will be most helpful.
I'd say such a report should contain at least the following:
* statement that says that all test types previous to UAT have been performed completely and no (blocking) bugs remain unsolved
* statement that all test cases for UAT have been created and have been approved by stakeholders (if applicable)
* statement that the application under test has been successfully deployed from development into test (assuming that UAT is done in an acceptance environment). This shows that the software can be deployed successfully (deployment test)
* statement that all necessary resources (time, people, infrastructure, etc.) needed for the UAT have been allocated
Keep it short but complete. As far as I'm concerned reports like these and especially the managers requesting them are the death of an agile and efficient testing process. Waste as little time on them as you can.
For large scale enterprise test phases they are essential. I'd say for smaller deployments they're also useful, unless you want to deploy into UAT and then suddenly find that you have no testers lined up...
Originally Posted by basd
microways, the level of detail will depend on the context of your UAT test phase and your client. For smaller deployments a simple checklist will be okay, and in larger deployments you'll need full-blown project plans to show your preparation and readiness.
I've attached a rough checklist that I've used before for UAT prep - the underlying .msp for the detail behind each task goes to around 2k rows so that might be overkill for you, but at least you'll get an idea of the different sections that need covering in your prep and might give you some ideas for creating your own checklist.
For the report, a simple dashboard in Excel showing the headline tasks as per your checklist, together with exit criteria from system integration testing and entry criteria into UAT, plus RAG status against each is usually effective. As your RAG status will change over time you'll find that a living report with your tasks down the rows, and weeks (or days if you get close) across the columns, is also effective, with the RAG status getting closer to overall Green the closer you get to deployment.
Here you cam find good templates of test plan and report:
Originally Posted by microways
I understand you want to shill your site, but you don't have a Test Readiness Plan there as requested by the original poster. Please at least answer the question in your answer, or don't reply...
Originally Posted by masukevic