Thank you.
Will do.
Would I impose too much if I also ask the following questions:
• Some tests rely on the server emulator running in the background.
Currently the emulator is started before the maven test phase and shut down
after. Is it acceptable? Or should I exclude such integration tests into a
separate profile?
• The server emulator is a JAR which is not available through maven
ecosystem as yet. It is proprietary. The code might be released in the
future, but there is no confirmation as yet. Is it OK to include it in a
projects folder - i.e. libtest? Not sure how licensing affects this. What is
the alternative in terms of testing? Or should I keep the tests, but exclude
them from the normal round, just provide the doco how to obtain and start
emulator?
• OnCompletion might raise a RuntimeException - should it be caught
instead?
It might result in a duplicate message as the server will resend the
message that was not acknowledged.
• Should I split integration (relying on the server emulator) and unit
(not
relying) tests?
--
View this message in context:
http://camel.465427.n5.nabble.com/New-component-comtribution-guidance-required-tp5789174p5789335.html
Sent from the Camel Development mailing list archive at Nabble.com.
