one of the main proposition of XP is wrting test code before coding ? can it be applicable to all the situations ? If it is bnot possible to write it fro each & every siotuations , then what are the parameters to identify the important stages of project , especially in iterative kind of projects , where the requirements are coming everyday & time to market is very important ?
I am a firm believer that trying to write the test first will cause you to write better code. The thought process required to figure out how to test a function will force you to expose the essence of the feature. I can not think of a situation where writing the test first is not the right thing. I, like Martin will do some html without writing the test first. But, I know I am doing the wrong thing. I know how to test the html, but sometimes I am just a bad person. When we are dealing with anything beyond a simple web page, the advantages in writing the tests first: the speed gain, the increase in accuracy, the qualitative improvement in the code itself completely overwhelm the effort required to write the tests. chet ------------------ author of: Extreme Programming Installed(The XP Series)
author of:<BR><A HREF="http://www.amazon.com/exec/obidos/ASIN/0201708426/electricporkchop" TARGET=_blank rel="nofollow">Extreme Programming Installed(The XP Series)</A>
permaculture is giving a gift to your future self. After reading this tiny ad:
professionally read, modify and write PDF files from Java