db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2667) Create more robust junit TestRunner for running derby tests
Date Fri, 18 May 2007 14:38:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496888

Daniel John Debrunner commented on DERBY-2667:

Not sure if "robust" is the right tem here, do you really mean a "more informative" test runner?

junit.textui.TestRunner does in fact print chained exceptions, it's Derby that is not chaining
the exceptions. I had a fix that did chain the exceptions but it broke on jdk16 so it was
backed out and put into a Jira entry which I think has yet to be fixed. DERBY-2472

For the separate file issue, have you looked at the way ant runs junit tests? We have the
top-level junit-all target and that provides a whole lot of information in XML that can help
in diagnosing issues. It's also standard so that others tools know how to handle the information,
e.g. CruiseControl presents the ant junit task output as web-pages complete with sections
for failed tests etc.

> 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:
>            Reporter: Kathey Marsden
>            Priority: Minor
> 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.

View raw message