[jira] Commented: (DERBY-2667) Create more robust junit TestRunner for running derby tests

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

Knut Anders Hatlen commented on DERBY-2667:
-------------------------------------------

Thanks Ole! This looks useful to me.

Committed JUnitMethodTrace.diff.txt with revision 552046 after resolving a conflict with another commit in TestConfiguration. I also removed the two new instance variables in BaseTestCase since testCaseName could be accessed through getName(), and the call to TestConfiguration.getCurrent().doTrace() should happen in runBare() (calling it from the constructor could cause the wrong TestConfiguration object to be used).

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