[
https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272284#comment-15272284
]
Quinn Stevenson commented on CAMEL-6132:
----------------------------------------
Sounds Good - but I have a question on the example.
I've used Pax Exam in two different scenarios, and I'm not sure which one is
the right one for the example.
In one case, I use the Pax Exam tests in the same module where the code I'm
testing lives. In the other case, the Pax Exam tests are in a completely
separate module, and just use the jar for the component they are testing. Both
uses have their merits/downfalls - but I'm not sure which one makes the most
sense for the example.
One thought I had was to update the blueprint example with a Pax test to
demonstrate the first scenario and then have the example projects demonstrate
the second usage.
Thoughts?
> camel-test-karaf - To allow end users more easily do Camel and Karaf
> integration test
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-6132
> URL: https://issues.apache.org/jira/browse/CAMEL-6132
> Project: Camel
> Issue Type: New Feature
> Components: karaf
> Reporter: Claus Ibsen
> Assignee: Quinn Stevenson
> Fix For: 2.18.0
>
>
> We should introduce a proper camel-test-karaf component that *end users* can
> use to do Camel and Karaf integration tests.
> The code we have in tests/camel-itest-karaf is for internal usage and testing
> of Camel. The code is not polished and intended for end users.
> We should create a new module for that, and take the good parts of
> camel-itest-karaf and make it user friendly etc. And of course have docs to
> go with as well.
> And when its good, we can use that in camel-itest-karaf also (eat our own dog
> food)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
