db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manjula Kutty" <manjula.ku...@gmail.com>
Subject Re: [jira] Commented: (DERBY-2667) Create more robust junit TestRunner for running derby tests
Date Fri, 22 Feb 2008 18:41:00 GMT
I created the patch using Eclipse and did click the source/correct
indentation. Is there a better way to fix this problem? Please let me know,
then I will do the same and will update the patch.

Thanks
Manjula


On 2/22/08, Knut Anders Hatlen (JIRA) <jira@apache.org> wrote:
>
>
>    [
> https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571303#action_12571303]
>
> Knut Anders Hatlen commented on DERBY-2667:
> -------------------------------------------
>
> Thanks for addressing my comments. Please double check the indentation
> settings in your IDE, though. The latest patch reintroduced the strange
> indentation from the earlier patches (each line starts with eight space
> characters, but for some reason tabs are appended if more indentation is
> needed).
>
> > 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_diff_02_21.txt,
> DERBY-2667_diff_2_19.txt, DERBY-2667_stat_02_06.txt,
> DERBY-2667_stat_02_15.txt, DERBY-2667_stat_02_19.txt,
> DERBY-2667_stat_02_21.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.
>
>


-- 
Thanks,
Manjula.

Mime
View raw message