How much time is/should be alloated for Testing out of total Development time based on industry standards?

  • Interview Candidate
  • 16
  • 4083

Showing Answers 1 - 16 of 16 Answers

srinivas

  • Aug 31st, 2005
 

Based on the project, which is specified in test plan and min. is 25% out of total dev. time.

James

  • May 5th, 2007
 

It is 3:1
i.e., If the developing is one day means the testing will takes 3 days.

twells185

  • Sep 18th, 2007
 

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?

  Was this answer useful?  Yes

surendra_kumar

  • Jun 15th, 2008
 

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.

sanuraj

  • Jul 2nd, 2008
 

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.

DVNRAO

  • Sep 10th, 2008
 

The testing estimation was very simple as per Industry standard practice. The inputs for this process , provided by the development team, where : the size of the Dev team and the number of working days needed for building a solution before starting systems tests.

The testing estimation process said that the number of testing engineers would be HALF of the number of Dev Team and one third of the total number of Development days / hours.

Take a look at the below formula:

Testing Working days = (Development working days) /3
Test engineers required = (Development engineers) / 2

Testing Cost = Testing Working days * Test engineers * Test Engineer daily cost.

I hope this helps..

lmktest

  • Nov 10th, 2008
 

General industry standard is 40% of total Project time. It may vary depending on the project and also the type of testing to be performed

  Was this answer useful?  Yes

anilmshinde

  • Oct 20th, 2009
 

There is no standard defined to estimate the testing efforts as it's governed by number of factors. Team's velocity is the used to measure on an average how many user stories a team can deliver in a sprint. Same principle can be used to decide how many user stories can be tested in a sprint. Based on experience in few sprint's velocity for testing can be derived.

  Was this answer useful?  Yes

rohan.satpute

  • Feb 6th, 2011
 

It depends upon following Factors:
1. Type of Project/Delieverable.
2. Scope of Testing.
3. Types of Testing to be Performed.

Testing can vary for 30%-50% of total Development Time. I have considered the case of Manual Tesing here. Automation can reduce the end delieverable timelines.

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions