In our company,we have lot of small projects.But we don't have any proper requirement or solution docs.We have only templets & the mail conversation between the client & our PM. We have only minimum time to test.
What can i do to test the project effectively?
Have these projects been been completed or are they still on the build?
If they are still on the build, then you could do something called "daily build and smoke test".Run some Smoke tests, to cover the major functionality for Breadth rather than Depth.
Run through some tests and give it a new name called Sham tests.
Thank u so much for ur responses.
Now i am very clear about how to manage small projects.I had a discussion with my PM & ask him to give all the details they have provided to the developer.Now I am also in group,whenever our team have call with the client.This is very useful & meaningful.Thank u so much
Is there sufficient information in the mail conversation (oh my!) to unambiguously test for the expected functionality?
You may want to talk with the PM to understand how they are interpreting the information from client and passing it on to the development team.
You may want to talk to the development team to find out what they are developing against.
Somehow, somewhere, there's a trail of communications that is sufficient for the work to get done and done correctly.
If not, then it's likely the client is VERY UNHAPPY! in which case, you shouldn't have any trouble convincing the PM that a) more thorough project documentation is needed, b) you need to be in the loop when they are talking to either the client or the developers, c) you need more time to test.
It's possible to streamline the documentation significantly, combining a Business and Functional Requirement for example.
We have a process that applies to any changes projected to take < 80 hours total project effort. There is a single document that describes the problem and the proposed solution. There is sufficient information in the document to allow developers to do their work and for QA to do their testing. The test documentation is correspondingly streamlined. A simplified test plan, the necessary test cases, etc.
You end up executing an abbreviated regression and checking the specific changes indicated by the documents.
This works as long as the application is well understood and the process is followed.