[
https://issues.apache.org/jira/browse/SHINDIG-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596833#action_12596833
]
Kevin Brown commented on SHINDIG-221:
-------------------------------------
A separate AllTests for each artifact is fine (the code is tiny), and in fact
that is the desired behavior. There's no good reason to require running gadget
rendering tests when you build the RESTful API, and there's no reason to run
RESTful tests when you're building the gadget renderer.
On the other hand, running both artifact's tests is a requirement if anything
in the common artifact is changed, so if there is going to be only one
AllTests, it belongs in the common artifact, NOT gadgets.
> Add an AllTests suite for running tests from Eclipse
> ----------------------------------------------------
>
> Key: SHINDIG-221
> URL: https://issues.apache.org/jira/browse/SHINDIG-221
> Project: Shindig
> Issue Type: Test
> Components: Common Components (Java)
> Environment: Linux/Eclipse
> Reporter: Dave Smith
> Priority: Minor
> Attachments: SHINDIG-221-AllTests.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Getting coverage numbers from within Eclipse needed an AllTests suite, so I
> wrote one.
> junit-addons provides DirectorySuiteBuilder.
> Note that because of the way the code is structured, the tests in the
> org.apache.shindig.util package don't get run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
