[CONF] Apache Camel > Camel 3.0 - Roadmap

[confluence]

Camel 3.0 - Roadmap Page edited by Hadrian Zbarcea Changes (5) ... h3. Tasks for camel-2.x (prepare) h4. Example task (champion) h5. Endorsements +1: [~muellerc] -1: [~hadr...@apache.org] h4. Improve the test api for testing components (jwcarman) The Camel's hump is an ugly lump Which well you may see at the Zoo; But uglier yet is the hump we get From having too little to do. (References) [CAMEL-9001|http://www.kipling.org.uk/poems_hump.htm] See [CAMEL-6029|https://issues.apache.org/jira/browse/CAMEL-6029]. 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. h3. Tasks for camel-3.0.0 (execute) ... Full Content Camel 3.0 Roadmap This page contains a summary of the ideas planned for the camel-3.0.0 release. Tasks for camel-2.x (prepare) Improve the test api for testing components (jwcarman) See CAMEL-6029. 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. Tasks for camel-3.0.0 (execute) Tasks for camel-3.x (finalize) Change Notification Preferences View Online | View Changes | Add Comment