CalSoft Pvt. Ltd.

Software Testing Estimation

Technique

Software Test Estimation Technique

Contents
Ad-hoc & Experience based estimation.................................................................2
Estimation Table................................................................................................. 2
Statistical method based estimation.....................................................................3
Program Evaluation & Review Technique............................................................3
Percentage of Development Effort......................................................................3
WBS or FP based estimation..................................................................................4
Work Breakdown Structure.................................................................................4
Function Point..................................................................................................... 4

CALSOFT Pvt Ltd.

Page 1 of 5
Confidential For Authorized Use Only
This document contains confidential information and is for the sole use of Calsoft. Unauthorized
distribution of this document without prior consent of Calsoft is subjected to legal action per laws.

CalSoft Pvt. Ltd.

Software Testing Estimation

Technique
Software Testing Estimation Technique can be broadly classified into 3 types:
1. Ad-hoc and Experience based estimation
2. Statistical method based estimation
3. Function-Point and Work breakdown structure (WBS) based
estimation

Ad-hoc & Experience based estimation

In Ad-hoc or best guess estimation, the test efforts are based on tentative
timeframe. The timeline is set by Test Manager or Product/marketing personnel
or by the Client without any prior experience. This kind of estimation has error
margins of over 100% - 200% at times.
Alternately, experience based estimation is based on analogies & metrics
collected from previous similar work done. Inputs are taken from SME who know
the application very well or an expert in testing domain. Such kind of estimation
usually has error margins of over 50% - 100% at times.
In Storage, Virtualization & Networking domain, having done many projects with
good amount of experience time, it has become easier to estimate based on this
experience. A table below depict different types of tests & its experience based
estimates.

Estimation Table
Type of
Testing

Difficulty
Level

Weightage

Test Case
development
rate per day

UI Testing

Simple

15-25

Test Case
Execution
rate per
day
10-15

Regression
Feature /
legacy feature
Testing
New feature
testing
Performance
Testing

Medium

5-8

3-5

Less Complex

4-6

2.5-4

Complex

3-5

2-3

Note: The above estimate is based on an average experience Tester with

experience of 3-6 Years. The TC development & execution rate will differ based
on testers experience.
CALSOFT Pvt Ltd.
Page 2 of 5
Confidential For Authorized Use Only
This document contains confidential information and is for the sole use of Calsoft. Unauthorized
distribution of this document without prior consent of Calsoft is subjected to legal action per laws.

CalSoft Pvt. Ltd.

Software Testing Estimation

Technique
Regression testing should be considered for a feature or a system as a whole.
This does not include GUI/CLI validation testing or workflow testing.

Statistical method based estimation

Program Evaluation & Review Technique
Most commonly used technique is 3-Point estimate technique a.k.a PERT
(Program Evaluation Review Technique). In this technique, work is broken down
into smaller elements using Work breakdown structure & each task/sub-task is
estimated using this mathematical formula:
Estimate (E) = ( a + (4*m) + b )/ 6

a = Optimistic Estimate (Best case scenario in which nothing goes

wrong and all conditions are optimal.)
m = Most Likely Estimate (most likely duration and there may be some
problem but most of the things will go right.)
b = Pessimistic Estimate (worst case scenario in which everything goes
wrong.)
E.g. If a=20 mandays, m=30 mandays & b=60 mandays, then
E= (20 + (4*30) + 60) / 6 = 33 mandays

Percentage of Development Effort

Another method is Percentage of development effort method. In this
method, there are some assumptions made. For example, a complex application
may require more testing effort & is directly proportional to the percentage of
development effort. The development effort is usually measured in LOC (Line of
Code) or FP (Function Points).

Example: If a previous project with 500 FPs required 50 man hours for
testing, the percentage of testing effort is calculated as:
P = (Total Actual Effort/FP) * 100, Alternately, TAE= FP * (P/100)
In this case: P = (50 / 500) * 100 =10%
For the current project with a development effort, say 1500 FPs, the
testing effort is:
Total Actual Effort, TAE = 1500 * (P/100) = 1500 * (10/100) = 150 man
hours.
CALSOFT Pvt Ltd.
Page 3 of 5
Confidential For Authorized Use Only
This document contains confidential information and is for the sole use of Calsoft. Unauthorized
distribution of this document without prior consent of Calsoft is subjected to legal action per laws.

CalSoft Pvt. Ltd.

Software Testing Estimation

Technique

WBS or FP based estimation

Work Breakdown Structure
WBS is created by breaking down the test project into small pieces. Modules are
divided into sub-modules. Sub modules are further divided into functionalities
and functionalities are divided in sub-functionalities. Review all the requirements
from Requirement Document to make sure they are added in WBS. This is also
known as Delphi Technique.

Function Point
The Function Point technique is a direct indicator of the functionality of
software application from the user's perspective. This is the most
accepted technique used to estimate the size of a software project. Basis
of this technique is function point technique. Here we convert function
points into test points.
In Test Point analysis, we usually carry out the following:
1. Dynamic Test Points
2. Static Test Points
3. Environmental Factor
4. Productivity Factor
5. Primary Test Hours
6. Control Factor
7. Total Test Hours
In Testing, this estimation is based on requirement specification
document, or a previously created prototype of the application.
Number of Test cases = [Number of Function Points] * 1.2
Example: In case of 500 FP, the total number of test cases will be 500*1.2=600
Total Actual Effort, TAE = (Number of Test cases) * (Percentage of
development effort /100)
Example: In case of 10% dev effort; TAE = 600*10/100 = 60 mandays
CALSOFT Pvt Ltd.
Page 4 of 5
Confidential For Authorized Use Only
This document contains confidential information and is for the sole use of Calsoft. Unauthorized
distribution of this document without prior consent of Calsoft is subjected to legal action per laws.

CalSoft Pvt. Ltd.

Software Testing Estimation

Technique

This method is done in a case when a detailed low level design document
or requirement document is available (i.e. measure of function point is
available) & previous data for development and testing is available.
In this FP technique we have to give weightage to each functional point.
Prior to starting actual estimating tasks, functional points are divided into
three groups like Complex, Medium & Simple. Based on similar projects &
Organization standards we have to define estimate per function points.
Total Effort Estimate = Total Function Points * Estimate defined per
Functional Point

Lets take a simple example to get clearer:

Weighta
ge

Function
Points

Total

25

20

60

35

35

Complex

Medium

Simple

Total Function Points 120

Estimate defined per Functional 4.15

Point (in
Hrs)

Total Estimated Effort (Man

Hours) = FP*Estimate per FP
(120*4.15)

498

CALSOFT Pvt Ltd.

Page 5 of 5
Confidential For Authorized Use Only
This document contains confidential information and is for the sole use of Calsoft. Unauthorized
distribution of this document without prior consent of Calsoft is subjected to legal action per laws.