Re: Camel - Test driven development

[Bilgin Ibryam <bi...@gmail.com>]

Writing tests always require extra effort, but in return it gives
confidence in the code. It is a cost/benefit judgment.

If you unit test your routes, it verifies the behavior of the route
regardless of the runtime environment (Servicemix or Fuse). But your will
need also some integration tests to verify whether the endpoint
configurations are correct and whether runtime wiring is in place.

HTH,



On 31 March 2014 05:04, Gnanaguru S <gn...@gmail.com> wrote:

>
> What is the benefit of Unit testing Camel routes before creating the
> context
> ?
>
> In terms of test driven developement, Before writing my camel context Lets
> say I am writing 5 unit test cases to test my routes.
>
> Also Lets assume the runtime is Fuse/Servicemix. In this kind of
> containers,
> is test driven development a advantage or disadvantage in Camel development
> point of view ?
>
> Camel is rich in components, It helps to connect hetergenous systems
> through
> its components. Configuring components takes it time, Although writing unit
> test cases isnt a double effort ? ( In case of test driven development ) /
> Effort which can drag the development cycle ?
>
> Just thought of brain stroming this topic in this Camel forum, because it
> may help many developers to understand its significance.
>
> Cheers
> Guru
> gnanaguru.com
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Test-driven-development-tp5749539.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Bilgin Ibryam

Apache Camel & Apache OFBiz committer
Blog: ofbizian.com
Twitter: @bibryam <https://twitter.com/bibryam>

Author of Instant Apache Camel Message Routing
http://www.amazon.com/dp/1783283475