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 17:41:16 GMT

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

Daniel John Debrunner commented on DERBY-2667:
----------------------------------------------

I think most of those requirements are fulfilled by the ant junit task, except for the last
one, which as you say is a test issue not a test runner issue.

I don't see any memory issues running junit-all, I run it as a continuous integration test
against Derby. I am getting a few tests failing but have only just started looking into that.

Note that with the first one I'm looking at the lack of information in trying to solve the
failure is not due to a test runner issue, but Derby not providing any information, e.g. I
just entered DERBY-2671 for the bug where early failures in starting the network server are
lost.

I think that dependance on a single junit test runner is not a good approach,  Derby and the
tests themselves should be providing information that can be useful in any test runner. Diversity
in test runners may also expose bugs in Derby, e.g. I would say that I only entered DERBY-2671
because I was running in a different test runner to my usual use of the swing one.

> 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
>
> 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.


Mime
View raw message