[
https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703914#action_12703914
]
Kathey Marsden commented on DERBY-2667:
---------------------------------------
Several improvements have been made under this issue over several releases,
actually none to the TestRunner itself. I am thinking resolving it now so
more specific issues can be opened and resolved in the release where they were
fixed. There is one outstanding patch from Kristian that would be very useful,
but the patch no longer applies to trunk.
Should I leave this open until that makes it in, or just close this one out and
open a new one to print the failure trace to the fail directory as they happen?
> 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-WriteExceptionsToFileAsTheyHappen.diff,
> 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.
