camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <willem.ji...@gmail.com>
Subject Re: Camel - Test driven development
Date Mon, 31 Mar 2014 05:36:36 GMT
As Camel route provides some abstraction of message routing, when you write the route, you
don’t need to take care of the component implementation. All you need to do is make sure
the camel route works as you expected first. 

With the help of camel unit test, we can make sure the camel route works, then you can add
more integration test to make sure the camel component works as you expected. 

--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem



On March 31, 2014 at 1:27:48 PM, Gnanaguru S (gnanagurus@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.
>  


Mime
View raw message