camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ranx <>
Subject Re: CamelBlueprintTestSupport version
Date Tue, 16 Feb 2016 17:05:47 GMT
Overall I like the design of CBTS.  I like the veracity of Pax Exam but don't
care for all the moving parts.  I'm sure it would be quite a headache to
fork CBTS and replace PojoSR with Karaf but to me that would be the best of
both worlds.

By definition any Camel testing is really integration testing, they are
rarely unit tests in any meaningful sense.  With all the configuration
issues, classloader issues, etc. it makes it tough to test and deploy the
same code.  I end up debugging CBTS tests a lot and then find out that
something doesn't work right in deployment anyway.

Personally I'm willing to live with slower running tests if I get more
veracity from them. 

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message