There is no such standard mentioned anywhere in the industry as such this much amount of time must be spent on the Testing task. It wholly depends upon the application and its criticalities. There are cases that require more time for testing compared to development time.
Above answer was rated as good by the following members: subam, Sanju_N
RE: How much time is/should be alloated for Testi...
So, when using a % of development hours to estimate testing hours (40% for example), what type of testing is included in that figure? Functional only? What about for UAT? Further, how should the 40% be broken down? What % for preparation of tests (cases, etc), what % for execution and what % for defect tracking? Any good guidelines?
RE: How much time is/should be alloated for Testing out of total Development time based on industry standards?
There is no such standard mentioned anywhere in the industry as such this much amount of time must be spent on the Testing task. It wholly depends upon the application and its criticalities. There are cases that require more time for testing compared to development time.
RE: How much time is/should be alloated for Testing out of total Development time based on industry standards?
As per the standerd we are following, the testing process is starting at the same time development starts. When they start developing testers are starting to prepare Test Scenarios and Test cases. Once these documents get approved we are starting testing the project as a whole or the modules which is completed development. So that developers can fix the bugs also by the time of developing. Once the whole project is completed we do integration testing, system testing, installation testing,UAT.
1 
0