[
https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570367#action_12570367
]
Myrna van Lunteren commented on DERBY-2667:
-------------------------------------------
I am wondering why you choose to only catch Exceptions?
For instance, a 'normal' failure would be likely a Throwable, e.g. a
junit.framework.AssertionFailedError...
Maybe it makes sense to save derby.log when a Throwable is encountered?
> 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_stat_02_06.txt, DERBY-2667_stat_02_15.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.
