Why start testing Early ?

  

 

  • Fact One

 

Let 's start with the regular software development life cycle :    

 

                                                                                               Source CTG - STBoX

 

    • First we 've got a planning fase : needs are expressed, people are contacted, meetings are booked.  Then the  decision is made : we are going to do this project.

    • After that analysis will be done, followed by code build.

    • Now it 's your turn : you can start testing.

 

Do you think this is what is going to happen ?  Dream on. 

 

This is what's going to happen :

                                                                                               Source CTG - STBoX

 
    • Planning, analyses and code build will take more time then planned.
    • That would not be a problem if the total project time would prolonge.  Forget it, it is most likely that you are going to deal with the fact that you will have to perform the tests in a few days.
    • The deadline is not going to be moved at all : promisses have been made to customers, project managers are going to lose their bonusses if they deliver later past deadline,...

 

  • Fact Two

 

The earlier you find a bug, the cheaper it is to fix it. 

 

        

                                                                               Source Compuware

 

If you are able to find the bug in the requirements determination, it is going to be 50 times cheaper (!!) than when you find the same bug in testing.

It will even be 100 times cheaper (!!) than when you find the bug after going live.

 

Easy to understand : if you find the bug in the requirements definitions, all you have to do is change the text of the requirements.  If you find the same bug  in final testing, analyses and code build already took place.  Much more effort is done to build something that nobody wanted.

 

 

  • Conclusion : start testing early !

 

This is what you should do :

 

                                                                                 Source CTG - STBoX

  • Make testing part of each fase in the software life cycle

  • Start test planning the moment the project starts

  • Start finding the bug the moment the requirements are definided

  • Keep on doing that during analysis and design fase

  • Make sure testing becomes part of the development process

  • And make sure all test preparation is done before you start final testing. If you have to start then, your testing is going to be crap !

 

  • Want to know how to do this ?

Go to the Functional testing step by step page !

 

 

If you like what we're doing, link to us !

                              Home

 

Mastertesting.Net © 2008  
Ma