> what is your opinion about TDD? Is it suckles or not? Do you have any
> experience with this kind of development?
Having a comprehensive unit testing suite to help you find
mistakes faster and avoid regressions is usually a good idea,
do it.
TDD (as in Test Driven Development / Design) is a buzzword
that basically means that your software design methodology
is to write tests that fail and do the simplest thing that
could possibly work to make them pass.
My opinion: bad idea. Good software is designed by thinking
about the whole system, this encourages local thinking.
Read this post to see what TDD done wrong can turn into:
http://devgrind.com/2007/04/25/how-to-not-solve-a-sudoku/
Now, if you're implementing a protocol or a document
specification, writing the tests first is a good idea.
But this is not about using tests to *design* code.
> Do TDD in C make any sense?
TDD no, unit testing yes. If you want test helpers,
look at these ones:
https://github.com/silentbicycle/greatest
https://github.com/kr/ct
You can also just use assertions.
--
Pierre Chapuis
Received on Tue Oct 22 2013 - 21:13:54 CEST