[ http://issues.apache.org/jira/browse/DERBY-2006?page=comments#action_12446158 ] Rajesh Kartha commented on DERBY-2006: --------------------------------------
Tried the latest patch and was able to run the junitreport. It took about 30 mins to run the Junit tests, saw some Network server start timeout failures. Anyways with the current usage the junit test output goes to "trunk\junit ", so a repeat run of the 'junitreport' will overwrite the output from the previous run (?) I am wondering if we can modify the ant task to direct the test o/p into a directory name based on timestamp - this could help preserve the outputs from each run. Something like: <junitreport todir="junit/DerbyTest_<time-stamp>"> > 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, derby_2006_v4.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
