I'm not sure I've had any particular problems with Camel Blueprint Test Support except in the olden days when there were some race conditions. On the other hand, I do know that I have a bit of "Dr. it hurts when i do this..." relationship with CBTS where I simply won't create certain designs because they are hard to difficult to test. In some unit test cases that's a good thing because it is forcing you into good, testable designs. With CBTS though it can be the case that I'm doing it because I know CBTS will hiccup. But I use it all the time.
More specifically I don't use Processor/Exchange so all my handlers can be individually JUnit tested, I use the Camel Java DSL so I can separately test routes as plain Camel Test Support and then I use Camel Blueprint Test Support just for wire up and smoke testing to make sure everything is there. Mockito works well for mocking the OSGi services my bundle is using. So, I can't say I have any particular problems with tests. -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
