Geeks With Blogs
Development In a Tesseract Observations and Developmental Experiences
Currently I'm in the process of reviewing some code that was written and then had MbUnit tests written to back flush the requirements.  Since I'm part of a more traditional shop, the code has already been peer reviewed.  The tests, of course, revealed errors in the code that weren't caught as a part of the peer review; so the code was corrected and re-reviewed.  Of course, when the tests were reviewed, the tests were found to have errors, which precipitated further changes.

I addressed the approach we are using to fix this effect (although the fix won't be perfect due to the limitations of our process) in the post How to make the most of traditional peer reviews. Posted on Wednesday, September 12, 2007 8:26 AM Software Engineering | Back to top


Comments on this post: Why half implementations of TDD don't work

Comments are closed.
Comments have been closed on this topic.
Copyright © Steven Mitcham | Powered by: GeeksWithBlogs.net