test effort estimation
DESCRIPTION
TRANSCRIPT
![Page 1: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/1.jpg)
Test Effort Estimation
![Page 2: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/2.jpg)
Why Test Effort Estimation
Effort
Expected Testing outcome
![Page 3: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/3.jpg)
Estimate of what ??
![Page 4: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/4.jpg)
ResourcesTime
Skill
![Page 5: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/5.jpg)
Who does the Test Estimation?
![Page 6: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/6.jpg)
“Test Manager”
![Page 7: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/7.jpg)
Identifying the
compo
nents
Developing Test Plan
Identifying Task
Computing size
Esti
mating test Effort
Preparing Test Plan
Validating Estimation
Steps in Test Effort Estimation1
2
3
4
5
6
7
![Page 8: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/8.jpg)
Identifying the Components to be Tested
1
![Page 9: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/9.jpg)
Common Components
• GUI Controls• Screens• Functions• Reports
![Page 10: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/10.jpg)
Identifying a Test Strategy
2
![Page 11: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/11.jpg)
On what basis test strategies are formed?
![Page 12: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/12.jpg)
Based on the components indentified
![Page 13: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/13.jpg)
Functionality1
Functionality12
TestStrategy1
TestStrategy2
TestStrategy3
TestStrategy4
![Page 14: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/14.jpg)
Identifying the tasks to be performed
One time task
Repetitive activities
3
![Page 15: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/15.jpg)
One time tasks
– Preparing test strategy– Understanding
customer requirements
– Establishing communication plan
Repetitive tasks
– Identifying test condition
– Developing Test cases
– Generating Test Data
– Reviewing test condition, test case, test data
– Executing test cases
– Reporting test results
![Page 16: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/16.jpg)
Computing software sizeBased on complexity
4
![Page 17: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/17.jpg)
Levels of complexity Low complexity
Web applications Desktop applications
Medium complexity Two tier/three tier application
High complexity Multitier applications
![Page 18: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/18.jpg)
Estimating Test Effort
4
1
2
3
5
INPUTS
Test Effort
Durations Infrastructure Resources Expertise
requires
![Page 19: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/19.jpg)
The estimate of test effort Forwarded To
Management TeamAccept Reject
![Page 20: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/20.jpg)
Preparing test plan based on inputs
6
![Page 21: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/21.jpg)
Test plan is prepared based on:• Scope of testing• Risk involved• Test completion criteria• Deliverables at different stages• Scope of defect management• Requirements for the test environment
![Page 22: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/22.jpg)
Validating the estimate at the end of project• All assumptions are re-validated• Done after the project • Determines if the estimate is correct
![Page 23: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/23.jpg)
Challenges Lack of clarity Inaccurate estimation Delay in project delivery Lack of proper test
planning Lack of testing expertise Selection of wrong test
data Lack of proper planning
for the test environment
![Page 24: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/24.jpg)
Test effort estimation techniques Function Point (FP) Constructive Cost Model (COCOMO) Test Point Analysis(TPA)
![Page 25: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/25.jpg)
Function Point Analysis• Function points are a unit measure for
software• It involves breaking the system into small components which in turn identifies the function points
![Page 26: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/26.jpg)
The size of application is calculated using 5 major components External Inputs External Outputs External Inquires Internal Logical Files External Interface Files
![Page 27: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/27.jpg)
Benefits of FPA• Language and technology independent• Estimate cost, effort, schedules of projects
that use prototype and spiral models• Helps in project estimation
![Page 28: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/28.jpg)
COCOMO Model
• It categorized software products into three classes– Organic systems“refers to simple projects developed by a few experienced
team”
– Semidetached systems“refers to intermediate projects between organic and
embedded”
– Embedded systems– “refers to complex projects”
![Page 29: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/29.jpg)
COCOMO model equation
• Effort =a1 * (KLOC)• Tdev=b1*(Effort)
KLOC – the estimated kilo lines of code a1, a2, b1, b2 are constants for different categories of
software products Tdev is the estimated time to develop the software in
‘months’ Effort is the total development effort required to
produce the software in ‘programmer months’.
a2
b2
![Page 30: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/30.jpg)
Benefits of TPA
• Analyst independent• Tests quality characteristics
![Page 31: Test effort estimation](https://reader036.vdocuments.mx/reader036/viewer/2022081414/54bdb40c4a79590c778b4598/html5/thumbnails/31.jpg)
Thank you