[ http://issues.apache.org/jira/browse/DERBY-2006?page=comments#action_12446126 ] Daniel John Debrunner commented on DERBY-2006: ----------------------------------------------
Given that flat output and the out of memory errors seen, I wonder if the ant targets should be at a lower suite granurality than suites.All. There could be a target that ran the various _Suite tests as separate junit invocations, mimicing the suites.All. > Add JUnit and JUnitReport task as a target in Ant script > -------------------------------------------------------- > > Key: DERBY-2006 > URL: http://issues.apache.org/jira/browse/DERBY-2006 > Project: Derby > Issue Type: Test > Components: Test > Affects Versions: 10.3.0.0 > Environment: Any > Reporter: Yip Ng > Attachments: derby_2006_v1.diff, derby_2006_v2.diff, > derby_2006_v3.diff, example_output.zip > > > Ant has an optional tasks called JUnit and JUnitReport that runs JUnit tests > and produces JUnit report respectively. It will be nice to have these > mechanism incorporated into the Ant script so one can easily kick off a JUnit > test and view the result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
