Explain Test Estimation

  • Interview Candidate
  • 27
  • 6167

Showing Answers 1 - 27 of 27 Answers

Sanjaycomplete

  • Dec 11th, 2006
 

Test estimation is the process through which we estimate time and resources required for testing.To support it we write effort estimation sheet and Gannt Chart.

  Was this answer useful?  Yes

sudhakar2068

  • Dec 16th, 2006
 

Test estimation see for testing time, Scope of recovery, Risk Analysis, estimation and resources required for testing.

sudhakar kolla,

Email ID:kollasudhakar2005@yahoo.co.in.

Ph:+91-9819859346

  Was this answer useful?  Yes

cyber

  • Dec 22nd, 2006
 

Test estimation see for testing time and resources required for testing and estimating the cost for testing

  Was this answer useful?  Yes

srinivas

  • Apr 4th, 2007
 

hi buddy given very good answer, just need one help, i am working as TL in wisdomleaf, i am responsible for creating test estimation , so could u pls send me estimation sheet with example and gann chart, bec i need to create here for coming project.

  Was this answer useful?  Yes

mathan_vel

  • Sep 14th, 2009
 

Test Estimation is the Testing time and resources required for testing.

There are different kind of approach to estimate the Test


* Percentage-of-Development Approach

* Implicit Risk Context Approach

* Metrics-Based Approach

* Test Work Breakdown Approach

* Iterative Approach

  Was this answer useful?  Yes

kurtz182

  • Dec 8th, 2009
 

The two primary elements of test estimation are time and resources.  Your estimation needs to take both into account.

There are many questions you need to answer in order to do test estimation.  The more accurate and thorough your answers to these questions, the better your test estimation.
 

1) What modules or functionalities will be tested and how many testers are available to test them?  Of course, as functionalities increase and/or number of testers decrease, the more time it will take to throughly test the application.

2) What is the complexity of each of these modules or functionalities?  As the complexity increases, the more time and effort will be required to understand the application, create test plans, create test cases, execute test cases, regress test cases, and retest defects.

3) How many test iterations (test runs) will be required to complete the test project?
This is also related to complexity.  As an application becomes more complex, it will typically require more test iterations to reach the company's exit critera (the number of open defects by severity and priority that a company can live with).

4) How much time will be required by developers to produce fixes for new builds between test runs?  Complexity is also a factor here.  As an application becomes more complex, there are often more dependencies between modules and functionalities.  This often requires coordination between developers.  Consequently, this takes more time.  This is important because your estimation must also include the amount of time testers are waiting for the next build between test runs. 

5) What is the average number of defects that you anticipate will be found during each test run?  You may have already guessed that complexity is a factor here too.  The more complex an application, the greater number of defects will reach the test team when the application is released to them.   In addition, the more complex the application, the more likely that severe and high priority defects will be found in later stages of the test process. 

6) How reliable are cross-functional groups that provide deliverables to the test team that are of high quality and on a timely basis?  For example, if the business requirements miss important functionalities, then more time will be required to recover from this oversight.  Oftentimes, your history with these groups will help you decide how to handle these risk factors in your estimation.

7) Don't forget that an 8-hour day is not entirely devoted to core responsibilities.  Testers go to meetings, read and respond to emails, and do other activities that consume time throughout the day.  This needs to be factored into your estimation as well. 

The first thing I do in order to estimate test time and resources is to facilitate a business requirements review with all my testers.  By reviewing the requirements with them, it gives me a good idea about the complexity of the application.  At the end of this meeting, I assign functionalities to each tester.  I give them several days to pour over their requirements again and get a good feel for their areas and then I ask them how much time they believe they will need to 1) produce test plans, 2) produce test cases, 3) map requirement to test cases.  Typically, I will take these numbers and apply a multiplier to account for their optimism as well as overall risks. 

There is more to estimating than I have described in this answer, but I believe it gives you a good foundation to begin with. 

  Was this answer useful?  Yes

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