Test Plenty
The following is from an entry in my diary dated back to June of 2005:
Test yourself before you wreck your. One of the interview questions asked during my interview for my current position was, “what do you do when adding a new feature?” I went on about understanding the specification, writing a use case, writing a test case, implementing the code and writing some unit tests. That is a text book answer that you don’t necessarily learn in school. Like comments, unit testing is one of those good habits that fall by the waste side when developers feel the crunch. At my new job you won’t believe the testing involved. The testing of a feature takes me longer than the implementation of said feature. In addition to JUnit our company has a proprietary testing harness that essentially tests the complete application including system correctness by replaying user experiences. We do so much testing that I proposed we adopt the motto, Leave No Test Behind. Sometimes my comments are twice as long as code. My testing takes me triple the time of development. But you need to remember that the life time of the software is four times what is expected.