Re: C++ fluency
On May 6, 5:00 pm, Jeff Schwab <j...@schwabcenter.com> wrote:
Jerry Coffin wrote:
In article <76d32lF1c73b...@mid.individual.net>,
ian-n...@hotmail.com says...
[ ... ]
The theory is that you write tons of little tests, and you can
tell roughly how close to "done" you are by seeing how many of
them pass yet.
I'm sceptical about that. A lot of times, yes, but there are
enough exceptions that you should be wary.
And of course, if you're doing iterative development (which is
normally the case), you won't normally write the tests for the
functionality of the second iteration before the first is done.
What you're doing is test-first development (and IMHO is a
strong sign of a great developer), not test-driven development
(a misguided methodology that has sold a lot of books).
I'm not sure what you mean by "test-first" development. Before
I run my tests, I write both the test and the code it is too
test. (And before I write a line of code, I'll have done some
design work.) On the other hand, I definitely do insist that a
module pass its unit tests before being "exported"; in fact, my
make files insist on it. (The rule "run-test" is a
pre-condition for all of the rules which export anything.)
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34