This paper focuses problem faced in testing due to in appropriate estimation and provide strategies and techniques for making sure the estimation is treated as an analytical process. Today’s e-business applications impose new challenges for software testing. Some of the commonly known challenges are complex application scenarios, extensive third party integration, crunched testing life cycles and increased security concerns. These factors inherently make testing of e-business application far more complex and critical than conventional software testing. Every phase which is delayed in complete SDLC, the first item that is allowed to bleed is testing. So it really becomes important to come up with robust and accurate estimations. Traditionally, estimation of efforts for testing has been more of a ballpark percentage of the rest of the
development life cycle phases. For E.g.
Testing working days = (Development working days) / 3.
Testing engineers = (Development engineers) / 2.
Testing costs = Testing working days * Testing engineers * person daily costs
This approach to estimation is more prone to errors and carries a bigger risk of delaying the launch
deadlines.
Following are some of the major risk caused due to in accuracy in estimations
1) Risk of low quality deliverables
2) Loss of opportunities
3) Resource Burnout
4) Increase in attrition rate
5) Loss of Good will and Credibility