1) During this 5 months how many release is there in that project?
2) Suppose don’t brother about process means … you can directly test the main functionality what Abu mentioned.
3) Otherwise you can increase resource in that project.
Though the question is answered well by others. I would like to share my experience as it happens most of the cases.
Testing activity takes its own time regardless of pressures and prioritization. Usually application is developed under more pressure with less time prone to more number of defects. Obviously testing team always get time for iterations as application gets rejected. So keep it in view practically, one should prioritize test cases to conclude and reject the defective application, and rest of time parallel to development, test cases with less priority are to be executed quickly.
The situation of defective application gives signals to management that it requires more time.
Pressure does not work in this case: If an embedded device should undergo 24 hrs thermal test, one can not complete within one hour by keeping 24 devices in 24 furnace. It becomes one hour with 24 devices test only.
Suggestion: within stipulated what we should be able to achieve we shall make it clear to management and then try for assigned challenging task. If we can't do then some other people exist in world to convince the client and achieve it.
just need to concentrate on functional areas....after all quality does matter!.
If rapid development is possible, why don't we go for Rapid Testing!
4 eyes are better then 2 eyes.