[
https://issues.apache.org/jira/browse/CAMEL-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-6029:
-------------------------------
Fix Version/s: (was: 2.11.0)
3.0.0
2.12.0
> Add test support classes for unit testing components
> ----------------------------------------------------
>
> Key: CAMEL-6029
> URL: https://issues.apache.org/jira/browse/CAMEL-6029
> Project: Camel
> Issue Type: Improvement
> Components: camel-test
> Affects Versions: 2.11.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.12.0, 3.0.0
>
>
> (see the [3.0
> roadmap|https://cwiki.apache.org/confluence/display/CAMEL/Camel+3.0+-+Roadmap]
> )
> No matter what choices and changes we make in the core, many tests in
> components will start failing. That is because virtually all unit tests in
> components test much more than the component itself, by setting up routes,
> etc. A simple thing would be do create something like xyzTestSupport (where
> xyz in {"Component", "Configuration", "Endpoint", "Producer", "Consumer",
> "Language", etc... }), that test a respective area without setting up routes
> and possibly use a minimal CamelContext (w/o component discover and/or other
> features). Moving component unit tests to such a framework is not
> complicated, a bit tedious, but hopefully we'll benefit (yet again) from
> community contributions and gain new committers in the process. This is
> probably the first thing that should be done that will allow us to be more
> productive with the other improvements. It can also be done in 2.x and won't
> require any incompatible changes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
