• Home
  • When to start/stop Software Testing

When do we start Software Testing?

Based on the software project and the selection of a specific SDLC model, the testing activities can be performed in the different phases of the software life cycle.

There is a misconception that testing is done only when some part of the software is built. However, testing can (should) be started even before a single line of code is written. It can be done in parallel with the development phase, e.g., in the case of the V Model, development and testing activities are integrated. In the below, table we can see the mapping of the testing activities with the development phase.

Development PhaseTesting Activity
Requirement DesigningAcceptance test creation (for the validation of the stake holder)
Functional Specification (e.g. SRS document preparation)Test case creation
Implementation or codingUnit test case creation (usually created by developers to check the code)
Code CompleteTest case execution (by software testers)

When to Stop Testing?

This question – “When to stop testing” or “How much testing is enough” is very tricky to answer as we can never be sure the system is 100% bug-free. But still, some markers help us in determining the closure of the testing phase of the software development life cycle.

  • Sufficient pass percentage – Depending on the system, testing can be stopped when an agreed-upon test case pass percentage is reached.
  • After a successful test case execution – The testing phase can be stopped when one complete cycle of test cases is executed after the last known bug fix.
  • On meeting deadlines – Testing can be stopped after deadlines get met with no high-priority issues left in the system.
  • Mean Time Between Failure (MTBF) – MTBF is the time interval between two inherent failures. Based on the different stakeholder’s decisions, if the MTBF is large, one can stop the testing.


Leave Comment