Hi, In our team we use a mixture of JTest and JUnit framework. We like JTest ability to automatically generate and run test cases. We also depend on its ability to assess code test coverage.
The mixture comes at higher-level objects, which depend on another complex objects to be constructed. Since the composite structure of our higher-level object requires specific values during the initialization of each object, the random values picked by JTest are usually insufficient to provide good code coverage. That's where JUnit kicks in: we get the code coverage map from JTest for a certain class and write JUnit testcases that reach the lines of source code that were not touched by JTest. We then go back to JTest and adjust it to run both its own automated tests *and* the JUnit testcase for that particular class. At the end of this process, we extract a JTest report to verify that indeed all lines of source code were covered. Regards, Denilson Nastacio =========================================== [EMAIL PROTECTED] http://nastacio.home.att.net ----- Original Message ----- From: "Prabodh Goel" <[EMAIL PROTECTED]> To: "Cactus Users List" <[EMAIL PROTECTED]> Sent: Tuesday, November 05, 2002 11:29 PM Subject: Junit vs JUnitDoclet vs Jtest > > Hi All > > I am evaluating which unit testing method I should use > from Quality Engg. perspective. > > a. Unit test should have 100% code coverage > b. I should be able to compile all the unit tests > (given by developers) at module level as well as a > whole. > > I am evaluating JUnit, JUnitDoclet and Jtest. > > Has anyone used all of these ? If yes, please let me > know which one will be able satisfy both the > conditions > Do I need JProbe for code coverage ? > > TIA > prabodh > > __________________________________________________ > Do you Yahoo!? > HotJobs - Search new jobs daily now > http://hotjobs.yahoo.com/ > > -- > To unsubscribe, e-mail: <mailto:cactus-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:cactus-user-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:cactus-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:cactus-user-help@;jakarta.apache.org>
