On Mon, Sep 9, 2013 at 5:56 PM, AlanFoster <a...@alanfoster.me> wrote:
> @Claus - This is true when deployed to an OSGi container. However, within the
> context of camel testing this is not true. When using the camel testing
> framework you need to supply all of the camel routes within your
> `getBlueprintDescriptor`
>
> @fs I just wanted to add; In my experience i have found it is safer to test
> your deployed camel app end to end, and not rely on CamelBlueprintTests much
> - as they do not prove that your app will work when deployed to an OSGi
> container, or work at runtime when deployed to a real OSGi container.
>
camel-test-blueprint is not a substitute for integration testing on
the actual production like servers.
IMHO you must always do this to ensure it works on your production environment.
camel-test-blueprint makes development with blueprint much easier as
you can do much quicker Camel development, and unit tests. And you can
do debugging the same JVM etc. And much more.
Doing development and running in Karaf is a pain. Even with the
dev:watch command.
IMHO camel-test-blueprint is a huge win, and I know some companies of
ours that would hate us if we do not offer camel-test-blueprint. That
said, the OSGI communities should making development with OSGi much
easier and a pleasure, instead of what the state is here in the later
half os 2013 currently is.
Okay my development with OSGi is hard, rant is over (") comparing to
what the norm is today.
PS: Thought this reminds me, that we ought to offer a camel-test-karaf
which makes doing integration testing with Karaf and Camel easier. We
do have some code in tests/camel-itest-karaf we would need to dust off
and make nicer, and as well document. There is a JIRA ticket for that.
Again devlopment + unit test vs integration testing is IMHO two pieces
that you need to have. But the former should be very easy to do, and
camel-test-blueprint helps alot with that. Though unfortuntely it
cannot do 100% the same as Karaf container so there can be some cases
where you currently must deploy to karaf to do unit test also :(
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/camel-blueprint-unit-tests-tp5738925p5738960.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
