Gone are the days when the software testing used to be an additional role and responsibility of the developer. The complexity and size of the software has increased multi-fold and with that the types of testing and complexity of testing has also increased.
Table of contents
- Test Estimation Techniques
- Percent Of Development Effort
- Metrics Based Approach
- Implicit Risk Context Approach
- Iterative Approach
- Delphi Method
- Three Point Estimation
- TestCase Enumeration Based Estimate
- Task Based Estimate (WBS)
- Testing Size/Points Based Estimate
- Function Point Analysis
- UseCase Point Estimate
- Object Point Or Alogrithmic Technique
A typical approach to test estimation is for a project manager or QA manager to implicitly use risk context, in combination with past personal experiences in the organization, to choose a level of resources to allocate to testing. In many organizations, the 'risk context' is assumed to be similar from one project to the next, so there is no explicit consideration of risk context. (Risk context might include factors such as the organization's typical software quality levels, the software's intended use, the experience level of developers and testers, etc.) This is essentially an intuitive guess based on experience.
