Edit post Follow this blog Administration + Create my blog

When to start and stop testing?

May 3 2019 , Written by Harry Published on #TESTER

When to start and stop testing?


An early start to testing reduces the cost, time to rework and error-free software that is delivered to the client. However, in the Software Development Life Cycle (SDLC) testing can be started from the Requirements Gathering phase and lasts until the deployment of the software. However, it also depends on the development model that is being used. For example, in Waterfall model, formal testing is conducted in the Testing phase, but in the incremental model, testing is performed at the end of every increment/iteration and at the end, the whole application is tested.

Testing is done in different forms at every phase of SDLC like during the Requirement gathering phase, the analysis and verifications of requirements are also considered testing. Reviewing the design in the design phase with intent to improve the design is also considered as testing. Testing performed by a developer on completion of the code is also categorized as a Unit type of testing.

Unlike when to start testing it is difficult to determine when to stop testing, as testing is a never-ending process and no one can say that any software is 100% tested. Following are the aspects which should be considered to stop the testing:

  • Testing Deadlines.

  • Completion of test case execution.

  • Completion of Functional and code coverage to a certain point.

  • Bug rate falls below a certain level and no high priority bugs are identified.

  • Management decision.

Share this post
To be informed of the latest articles, subscribe:
Comment on this post