unit testing - Disadvantages of Test Driven Development? -
what lose adopting test driven design?
list negatives; not list benefits written in negative form.
several downsides (and i'm not claiming there no benefits - when writing foundation of project - it'd save lot of time @ end):
- big time investment. simple case lose 20% of actual implementation, complicated cases lose more.
- additional complexity. complex cases test cases harder calculate, i'd suggest in cases try , use automatic reference code run in parallel in debug version / test run, instead of unit test of simplest cases.
- design impacts. design not clear @ start , evolves go along - force redo test generate big time lose. suggest postponing unit tests in case until have grasp of design in mind.
- continuous tweaking. data structures , black box algorithms unit tests perfect, algorithms tend changed, tweaked or fine tuned, can cause big time investment 1 might claim not justified. use when think fits system , don't force design fit tdd.
Comments
Post a Comment