How you will Estimation time for testing the application and What process you use for it?

Replies to This Discussion

Permalink Reply by Prasad L V on April 14, 2010 at 5:16pm

Estimation:
1. Review the FS
2. Count how many test cases can be developed for each requirement
3. How much time takes to write test case for each requirement (in minitues).
4. Review time (if needed)
5. 1st iteration execution time, to execute each test case how much time takes (in minitues).
6. 2nd iteration execution time, to execute each test case how much time takes (in minitues).
7. caliculate minutes by hours and hours by days (in days).

you will get final count in Days.

• ▶ Reply

Permalink Reply by Madhukar M on April 14, 2010 at 7:32pm

the following are the process of estimating the time for testing the application.

By using metrics and classify the work,
work breakdown method
Functional Point Analysis.
Wideband approach

• ▶ Reply

Permalink Reply by Senthil SKrishnan on April 15, 2010 at 12:16pm

Estimation for testing activity in the project can also done based on Activity wise effort distribution goal of your organization. Something like 10% [of total efforts] for Req. gathering, 10% for prototyping, 25% for design, 30% for development, 15% for Testing, etc... These are just sample values & they differ from company to company.

So, whenever we have a normal development project with Testing as part of the project, the efforts taken to complete whole project will be estimated using some estimation techniques like Fp, Delphi, Bottom-up, etc.. and a % of total efforts will be allocated to Testing.

If it's a complete Testing project, then we go with estimating the testing cycles, what are all the types of testing to be done on the application, etc..

• ▶ Reply

Permalink Reply by Siddiq on April 15, 2010 at 12:20pm

I agree with Senthil.

• ▶ Reply

Permalink Reply by Prasad L V on April 15, 2010 at 12:37pm

appreciate senthil reply.
valuable information.
thanks

• ▶ Reply

Permalink Reply by Arun on April 15, 2010 at 1:14pm

Hi Madhu,

Can you explain about work breakdown method & Wideband approach detaily, with examples.If you have Materials can you forward me.

• ▶ Reply

Permalink Reply by Swarupa Rani on April 20, 2010 at 4:09pm

The two primary elements in test estimation are time and resources.
Your estimation needs to take both into account.
The value of the application to your customers and your company?
modules or functionalities with their complexity will be tested
How many testers are available to test them?
Number of test iterations (test runs) will be required to complete the test project?
Time to retest the bugs which are fixed by developers has to be tested again for correct functionality and for regression testing
Preparation of documents and reports do come under this Estimation

• ▶ Reply

Permalink Reply by krishna on April 20, 2010 at 5:54pm

Application = Req

Normally per day 8tcases u can design.(Normal Requirement)
8 hours/day.
1 hour / testcase.
but there are aspects like tcase review internal(0.50), Tc update internal(0.25), Client review(0,75) & implementation of client review (0.50)review.hence entirely it takes 3hours for a Correct development of a normal test case.
Test case execution other phase and time spent will be differnt here 6-8 tcases/day if it is System testcase & 14-16 Testcases if it is negative testcase.

• ▶ Reply

Permalink Reply by Praveen on April 22, 2010 at 9:08am

Yes you are right krishna..
But i am having one more concern, how does we analyze that how many test case will be developed for the particular functionality...
case1: If no requirement are given.. no idea about the application.
caaw2: If the requirement are given..
can you please explain with example..

• ▶ Reply