This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Unit test is good in many aspects. But do you think it much expensive to write full set of unit tests for our business methods, especially enterprise application business methods? The full set of unit tests include one or more ok test (a mediation business method require multiple ok unit tests), multiple data validation tests, multiple exception tests. Further, when you write in-container unit test, which is the most often seen condition for j2ee application development, you may experience pain on DbUnit, ServletTestCase or StrutsTestCase framework usage. After nearly half a year practicing on unit test and test-driven development, I am frustrated very much, because I spent much more time on writing unit test code than on writing the business method implementation. Can anyone tell me whether I should give up the unit testing?
On your way in you may have missed that we have a policy on screen names here at JavaRanch. Basically, it must consist of a first name, a space, and a last name, and not be obviously fictitious. Since yours does not conform with it, please take a moment to change it, which you can do right here.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus