Thank you Myrna, -Manjula
On 2/22/08, Myrna van Lunteren (JIRA) <[EMAIL PROTECTED]> wrote: > > > [ > https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571270#action_12571270] > > myrna edited comment on DERBY-2667 at 2/22/08 3:36 PM: > -------------------------------------------------------------------- > > Thanks Manjula, I like the latest patch. > > I committed patch DERBY-2667_diff_02_21.txt with revision 630077. > > Probably superfluous, but, I do want to point out that the > TestConfiguration.getFailureFolder creates a 'fail' folder, and all > directories underneath > (fail/<configuration>/<testName>/<failedFixtureName>). > This means, that if you run a subsequent failing fixture test in the same > top level directory, previous derby.logs will be overwritten, and also, > old run's fail directories won't get cleaned out. > > > was (Author: myrna): > Thanks Manjula, I like the latest patch. > > I committed patch DERBY-2667_diff_02_21.txt with revision 63007. > > Probably superfluous, but, I do want to point out that the > TestConfiguration.getFailureFolder creates a 'fail' folder, and all > directories underneath > (fail/<configuration>/<testName>/<failedFixtureName>). > This means, that if you run a subsequent failing fixture test in the same > top level directory, previous derby.logs will be overwritten, and also, > old run's fail directories won't get cleaned out. > > > > Create more robust junit TestRunner for running derby tests > > ------------------------------------------------------------ > > > > Key: DERBY-2667 > > URL: https://issues.apache.org/jira/browse/DERBY-2667 > > Project: Derby > > Issue Type: Improvement > > Components: Test > > Affects Versions: 10.3.1.4 > > Reporter: Kathey Marsden > > Priority: Minor > > Attachments: DERBY-2667_diff_02_06.txt, > DERBY-2667_diff_02_15.txt, DERBY-2667_diff_02_21.txt, > DERBY-2667_diff_2_19.txt, DERBY-2667_stat_02_06.txt, > DERBY-2667_stat_02_15.txt, DERBY-2667_stat_02_19.txt, > DERBY-2667_stat_02_21.txt, JUnitMethodTrace.diff.txt, > JUnitMethodTrace_Extra.diff.txt, MemRunner.java, TimeRunner.java > > > > > > Provide a more full featured TestRunner for Derby testing. > > junit.textui.TestRunner is not very robust. It does not for example > print the tests as they run or print chained exceptions, create separate > files for the full report and just failures. It would be great to have a > standardized TestRunner that everyone uses. Perhaps someone already has one > that they would like to contribute as a starter. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > -- Thanks, Manjula.
