db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manjula Kutty (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2667) Create more robust junit TestRunner for running derby tests
Date Thu, 07 Feb 2008 00:07:08 GMT

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

Manjula Kutty updated DERBY-2667:

    Attachment: DERBY-2667_diff_02_06.txt

Attaching a patch which will copy the derby.log file of the failed test to the dir user.dir/fail/clientname/testclass/testname.
Please review and if looks useful please commit

> 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
>         Attachments: DERBY-2667_diff_02_06.txt, DERBY-2667_stat_02_06.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.

View raw message