[
http://jira.jboss.com/jira/browse/JBPM-1203?page=comments#action_12416989 ]
Tom Baeyens commented on JBPM-1203:
-----------------------------------
i used to do a scan for tests in ant with includes excludes
since i use the AllTests during development. i neglected the includes/excludes and the
ant test suite was never in sync with the AllTests (as could be expected)
so i tried configuring the AllTests in the ant build.
the downside of that was that there was no structure in the test report. *all* test
methods of all tests were flat in the report.
don't know what the current situation is. but that is the background of what i
remember.
Remove aggregation tests
------------------------
Key: JBPM-1203
URL:
http://jira.jboss.com/jira/browse/JBPM-1203
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: jPDL 3
Reporter: Thomas Diesler
These types of tests are unnecessary
public class AllTests extends TestCase {
public static Test suite() {
try {
TestSuite suite = new TestSuite("org.jbpm");
//$JUnit-BEGIN$
suite.addTest(AllPojoTests.suite());
suite.addTest(AllDbTests.suite());
suite.addTestSuite(SerializabilityTest.class);
//$JUnit-END$
return suite;
} catch (Throwable t) {
t.printStackTrace();
return null;
}
}
ant as well as maven supports includes/excludes that are easier to maintain
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira