Is there any "conclusion document" once the testing is done? The scenario is the project I am working is going to conclude in a week. I am wondering if there is any conclusion document to be provided to the PM or the client. I would appreciate if some body could suggest me any concluding documents (if there are any).
I'm guessing that what your after is some sort of report to present at the end of testing to say how it went.
I'd suggest some of the key things to include in this report would be...
- Summary of featured delivered
- Summary of testing completed against these functions (how many tests, how many passed etc.)
- Things that didn't get tested and why
- Outstanding problems (which bugs did you raise that didn't get fixed and why)
Hopefully the development team will have produced a release note, so you may be able to use that to give you a steer, but basically you're trying to summarise what you did, what you didn't do, and whether it was ok.
The key thing to remember is: Don't download a template from the internet and fill it in. Think about who the report is for and what they need to know (maybe you could ask them) then write a report summarising this.
Note: If you're providing this to the client to form any sort of signoff against the software then make sure the PM reviews it before it goes to the client.