Test Maturity Model

What is Testing Maturity Model?

Based on the capability maturity model, the testing maturity model or TMM, helps to improve the potency of the testing process. Consisting of different levels, this is a suitable framework for holistically assessing the quality of the testing processes of a software product in an organisation.

What is the need for testing maturity model?

There are a number of advantages accrued to an organisation from following the testing maturity model. Some of them are:

  • When there is an improvement in maturity level of a software process, the software development lifecycle gets stabilized.
  • There is reduction in risks associated with software development.
  • Creativity gets focused in crucial segments.
  • There is an urgent need to institutionalise the best practices in software testing.
  • The model helps in evaluation of the best testing tools.

What are the levels in Testing Maturity Model?

Basically, the testing maturity model consists of 5 levels with different goals and adjectives.

TMM Levels Level Objective
Level 1: Initial This level is characterised by chaos. The testing processes cannot be easily distinguished from debugging and are ill defined. The organisation uses test cases built on an adhoc basis due to lack of trained testing professionals. Objective here is to show that the software is workable. The stage also lacks any form of quality assurance checks before the software product is delivered.
Level 2: Definition At this level, the testing processes and the debugging activities are well distinguished. The most basic of testing processes become well placed and properly defined. The goal of testing is advanced to a level which ensures that the software is meeting the specifications.
Level 3: Integration The reaching of this level is also a form of actualization for the company management to consider testing as a professional activity. Testing based on system requirements becomes an inherent part of the software life cycle. With the use of automated tools for testing, the whole process of verifying a software product for flaws becomes wholly organised.
Level 4: Management & Measurement With the attainment of this level, the testing activity becomes a measurable/quantifiable process. All the development phases in the product are reviewed as tests for valuable performance attributes such as reliability, usability, etc. This level is also highlighted with the collection of test cases and their recording in databases. The defects logged are assigned a severity and priority level for their rectification.
Level 5: Optimization Some of the best testing practices where automated tools become the norm are institutionalised. Efforts are constantly made to reduce the test costs and improve upon the effectiveness of the test processes by continuously fine tuning and monitoring them. Quality control and defect prevention are some of the other defining aspects of this level.