The software testing estimation technique is based on statistical methods. Each testing task is broken down into sub-tasks. Furthermore, three types of estimation are done on each sub-tasks.
Defining Software Test Estimation Technique
Test efforts are not based on any definitive time frame. This is mostly because conventionally, test effort estimation is a part of the development estimation. However, only in the case of estimation techniques that use WBS can you obtain the values for the estimates of the testing activities. For instance, Wideband Delphi, Three-point Estimation, PERT, and WBS.
Factors to Consider
- Team skills
- Domain Knowledge
- Complexity of the application
- Historical data
- Bug cycles for the project
- Resources availability
- Productivity variations
- System environment and also downtime
Techniques in Software Test Estimation
Wideband Delphi Technique
In Wideband Delphi Method, WBS is distributed to a team comprising of 3-7 members for re-estimating the tasks. Hence, the final estimate is the result of the summarized calculations based on the team consensus.
This method speaks more on experience rather than any statistical formula. Moreover, this method emphasizes the group iteration to reach a consensus where the team visualized different aspects of the problems while estimating the test effort.
PERT Software Testing Estimation Technique
PERT software testing estimation technique is based on statistical methods in which each testing task is broken down into sub-tasks, and then three types of estimation are done on each sub-tasks.
Work Breakdown Structure
- Create WBS by breaking down the test project into small pieces.
- Divide modules into sub-modules.
- Divide sub-modules further into functionalities.
- Division of functionalities into sub-functionalities.
- Review all the testing requirements to make sure they are added in WBS.
- Figure out the number of tasks your team needs to complete.
- Estimate the effort for each task.
- Estimate the duration of each task.
Function Point or Testing Point Analysis
FPs indicate the functionality of software application from the user’s perspective. In testing, estimation is based on a requirement specification document or a previously created prototype of the application.
Use-Case Point Method
UCP Method is based on the use cases where we calculate the unadjusted actor weights and, likewise, the unadjusted use case weights to determine the software testing estimation.
Use-case is a document that specifies different users, systems, or other stakeholders interacting with the concerned application. Hence, the interactions accomplish some defined goals protecting the interest of all stakeholders through different behavior or flow termed as scenarios.
In a software project, establishing goals and also commitments is a crucial factor. Knowing from the beginning of the development the objective you want to meet to fulfill your company’s commercial needs, as well as those promises (commitments) that a particular functionality or system will be ready by a specific date, are the basis for facing any estimation.
Many times, the estimations and restrictions of the project make achieving the proposed goals a bit complex. In these situations, it is essential to know and also consider the most significant functional priorities so that you can focus on the most critical topics.