• info@helpingtesters.com
  • helpingtesters

Benefits of Early Testing

December 17, 2016
early test, early testing, benefits of early testing

There is a lot to gain in early testing. Early testing is quite important. A defect can be found throughout all the phases of software development Life Cycle. So, it is better to start early Testing in the software development life cycle, so as to minimize defects in the later stages. It can be design review, unit testing or regression testing. Design phase comes early in Software development Life Cycle. Design Testing is done at this phase. 

This is the point where if not checked can lead to too much rework and maintenance at a later stage because it is the phase which decides the future course of action of the project. Development and testing phase of the software development Life Cycle come after Design phase. So, the whole course of development depends on Design phase in which how software will be developed is designed. 

Maximum Bug originates in Requirement

As per research was done by Analysts, it has been found that maximum defects occur in Requirement and Design Phase. More than half of the defect originates in Requirement Phase. It makes up to 56% of the total defects that is found in software development Life Cycle. 23 % comes in Design phase.7 % comes in the development phase and 10% defects originate in Regression testing and other sources.

Understanding of requirements

Even in a case of Agile testing, if a requirement is not correctly understood or recorded and incorrect user stories are prepared, it can lead to failure of Sprint. Though there is the problem in getting perfect requirement, but maximum attention should be given for getting clear requirement and requirement review should be done to ensure that it is proper with chances of minimal deviation.

Cost of Bug Fixing

It has been observed that not too much testing effort is done in preparing Proposal, Requirement phase, Design phase, Development phase and installation phase. Maximum testing effort goes in the testing phase. That’s why the cost of fixing a defect is maximum in such practice and incurs the highest cost in rework and maintenance of the software project. A customer can face heavy losses if the software delivered is not up to the mark and does not meet the customer expectation. 

It should be noted that most of the defects occur in the early phase of the software development life cycle but are found in the later stage of the development, which costs more than what it would take to fix the defect at an early stage of software development life cycle, say requirement review or design review. 

Analyzing of Requirements for Early Testing

It has been observed that costing of the bug fixing increases 10 to 100 times in the later stage of project development which points strong reason to undergo early testing. For example, if the tester is going through the requirement and he finds that validation error message is missing in the requirement and user does not get a message like “Invalid Username or Password” when a user enters incorrect Username or Password. The tester can get it added immediately so that there is no any mess during Development phase or testing phase where the tester is neither getting any error message nor the login page is redirected to welcome page or any other page.

Otherwise, if early testing would not have been done, then the developer would not have coded this feature and tester in the later phase of development would have reported it leading to rework by the development team and again testing would have been done to verify it.

Unit Testing 

So, from this example, we can see that little modification in requirement testing can prevent effort in rework in development and testing stage. Similarly, design testing can also prevent lots of effort in Development and Testing stages. Even unit testing after development prevents a lot of defects to come to testing phase and get removed then and there. 

Knowledge of Software Increases

Sooner we detect the issue, more the cost and effort are reduced at a later stage. Also, early Testing of software development makes the tester more familiar with the software and enhance their testing capability for that software and they can think of scenarios which could be possible only after a better understanding of software. Thus we see that in order to reduce the cost of the project, a cost of testing needs to be reduced and for that cost of bug fixing needs to be reduced.

Reducing Bug fixing Cost & Time

For reducing the bug fixing cost, early testing should be done in requirement and design phase in the form of review so that any defect, if it is there in early stages, is sorted out and removed then and there itself without further being carried to development and testing phase, which if occurs in development require more testing effort and bug fixing effort incurring more time, effort and cost to the organization.

Overall, we can say that in order to reduce Software testing cost, it is quite important to spend time more in early phases of software development i.e. early testing to make sure that requirement and design are up to the mark and correct, so as to minimise correction and modification rework effort during later stage of software development Life Cycle such as development and testing, thus saving time, effort and cost to the organization.



About the author

RamPrakash Singh author

Ram Prakash has worked in various domains of testing including security, performance, security testing and automation testing. Including several tools like QTP, selenium, LoadRunner,JMeter, VSTS Coded UI, soap UI, Burp Suite etc.

1 Comment


May 23, 2017 at 6:00 am

Information is power.

Leave a Reply

Your email address will not be published.