On Tue, Apr 8, 2014 at 8:35 AM, ayilliath <ayilli...@gmail.com> wrote: > Thanks! I tried cobertura too, however the report seems to be generated for > the java classes alone and not for the route in itself. I am not sure if I > am missing something or if this is what is expected. >
There is no tooling out of the box that can do "route coverage" reports. But you can capture this a bit using JMX, and there is a dump route statistics XML operation you can use to see how many invocations the eips in the routes has been invoked. http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/api/management/mbean/ManagedCamelContextMBean.html#dumpRoutesStatsAsXml(boolean, boolean) > Thanks > Rakesh > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/test-coverage-tp5749876p5749920.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
