Afficher un message
Vieux 30/06/2008, 21h14   #13
Ian Collins
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: c++ class design: where to put debug purpose utility class?

Phlip wrote:
> Ian Collins wrote:
>
>>> Where we
>>> disagree is that you seem to consider the unit tests a form of
>>> being "written down", whereas I consider them code, just like
>>> the rest---I don't know how to write a unit test until I have
>>> some idea what is to be tested, i.e. what the unit shoud do.
>>> And IMHO, I don't know that until it is written down.
>>>

>> Not really, the written down will be some form of requirement, be that a
>> clause in a traditional requirements specification, or an XP style user
>> story. Given a requirement, my view of TDD is that it's another form of
>> functional decomposition. You know what your end gaol is, you know the
>> steps to take you there and you follow them. The smaller those steps,
>> the better.

>
> You American you!!


Two insults in one day, what am I doing wrong?

--
Ian Collins.
  Réponse avec citation
 
Page generated in 0,04424 seconds with 9 queries