When to Start Testing and When to Stop Testing ?

When to Start Testing ?

An early start to testing reduces the cost, time to rework and error free software that is delivered to

the client.

However in Software Development Life Cycle (SDLC) testing can be started from the Requirements Gathering phase and lasts till the deployment of the software. 

For example in Water fall model formal testing is conducted in the Testing phase, but in incremental model, testing is performed at the end of every increment/iteration and at the end the whole application is tested.

When to Stop 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:

oTesting Deadlines.

oCompletion of test case execution.

oCompletion of Functional and code coverage to a certain point.

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

oManagement decision.

Who does testing?

• It depends on the process and the associated stakeholders of the project(s). In the IT industry, large companies have a team with responsibilities to evaluate the developed software in the context of the given requirements. Moreover, developers also conduct testing which is called Unit Testing. In most cases, following professionals are involved in testing of a system within their respective capacities:

                     oSoftware Tester
                     oSoftware Developer
                     oProject Lead/Manager
                     oEnd User

• Different companies have difference designations for people who test the software on the basis of their experience and knowledge such as Software Tester, Software Quality Assurance Engineer, and QA Analyst etc.

What is testing?

• Testing is the process of evaluating a system or its component(s) with the intent to find that whether it satisfies the specified requirements or not. This activity results in the actual, expected and difference between their results. In simple words testing is executing a system in order to identify any gaps, errors or missing requirements in contrary to the actual desire or requirements.

• Testing is the process of evaluating a system or its component(s) with the intent to find that whether it satisfies the specified requirements or not.

• Testing is executing a system in order to identify any gaps, errors or missing requirements in contrary to the actual desire or requirements.

• This tutorial will give you basic understanding on software testing, it's types, methods, levels and other related terminologies.