river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-301) Move the tests into the JUnit framework inside the main source project
Date Fri, 27 Mar 2009 15:06:50 GMT

    [ https://issues.apache.org/jira/browse/RIVER-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689930#action_12689930
] 

Jukka Zitting commented on RIVER-301:
-------------------------------------

Good stuff! Committed in revision 758747.

Thanks also to Tom for the review and feedback, it gave me much more confidence to commit
the relatively large patch.

> Move the tests into the JUnit framework inside the main source project
> ----------------------------------------------------------------------
>
>                 Key: RIVER-301
>                 URL: https://issues.apache.org/jira/browse/RIVER-301
>             Project: River
>          Issue Type: Task
>          Components: other
>    Affects Versions: AR3
>            Reporter: Tom Hobbs
>         Attachments: integrationtest.xml, RIVER-301.patch, RIVER-301.patch, River-301.patch.zip,
River-build-qa5.patch
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> The tests donated by SUN live in their own source project and are runnable in a format
that is unfriendly towards IDEs and new developers to the River project.
> This is the proposal to move the test code, mostly unmodified, into the main source directory
whilst shoe-horning it into JUnit 3.  This will allow it to be easily viewable and runnable.
 Such a structure will also reduce the code-compile-test cycle since no JARs will have to
be created in the middle of the cycle and no long command-line incantations.

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