In order to achieve measurable improvements in QA processes in an organization we need a framework for evaluating the maturity of software testing processes. The purpose of using a testing maturity model is identifying maturity and providing targets to improve the software testing process to achieve progress. It can be complemented with any process improvement model or can be used as a stand alone model.
Different Levels of Maturity
The five levels helps the organization to determine the maturity of its process and to identify the next improvement steps that are essential to achieving a higher level of test maturity.
| Levels | Goals | An objective of the levels |
|---|---|---|
| Level 1: Initial | Software should run successfully | At this level, no process areas are identifiedAn objective of testing is to ensure that software is working fineThis level lacks resources, tools, and trained staff. No Quality Assurance checks before software delivery |
| Level 2: Defined | Develop testing and debugging goals and policies | This level distinguish testing from debugging & they are considered distinct activitiesTesting phase comes after codingA primary goal of testing is to show software meets specificationBasic testing methods and techniques are in place |
| Level 3: Integrated | Integration of testing into the software lifecycle | Testing gets integrated into an entire life cycleBased on requirements test objectives are definedTest organization existsTesting recognized as a professional activity |
| Level 4: Management and Measurement | Establish a test measurement program | Testing is a measured and quantified processReview at all development phases are recognized as testsFor reuse and Regression Testing, test cases are gathered and recorded in a test databaseDefects are logged and given severity levels |
| Level 5: Optimized | Test process optimization | Testing is managed and definedTesting effectiveness and costs can be monitoredTesting can be fine-tuned and continuously improvedQuality control and Defect prevention are practicedProcess reuse is practicedTest related metrics also have tool supportTools provide support for Test Case design and defect collection |

