Hi, I was wondering about the use of Java annotations for creating test cases for unit testing. It seemed to me that if you used annotations, you could embed your test cases in the source code, thus avoiding the problem of losing test cases, and keeping the test cases in front of the programmer so they'd be updated along with the source code. So I did some looking around.
It appears JUnit4 is still the way to go. Here's a link to the 10 minute explanation: http://www.instrumentalservices.com/content/view/45/52/#_Cut_the_chase_to%20JUnit%204.0 I think this is the way to go for unit testing in just about any Java project. As I said before, we don't have to go retrofit all the code. We could just add test cases as we work on modules. That way, we'll wind up instrumenting the most important modules first, since they'll be the ones worked on the most anyway. What do the rest of you think? Ray ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Freemind-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freemind-developer
