Currently in Maven we have two types of tests that a developer can use to partition test cases: 'unit tests' and 'integration unit tests'. We borrowed this distinction and definition from the Cactus project. Unit tests are logical tests that have no dependencies on any external systems to run. Integration unit tests are logical tests that do have some sort of dependency on an external system to execute. This may be a servlet container ( in this case we use cactus ) or a database, or some other external resource. In my experience the iutests often take longer to run than unit tests.
Currently in maven we've just automated starting up cactus for our iutests. I'm wondering if there's any ideas on how we can have this test execution portion not only limited to cactus tests ( and not have the cactus tests only limited to tomcat 4.x ). For example, I may have a situation where I have some cactus tests in my iutest suite for testing some of my servlet code. I may also want to test some torque om classes which actually hit a real testing database. Ideas? ================================================================= Jeffrey D. Brekke Quad/Graphics [EMAIL PROTECTED] http://www.qg.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
