My question, is why do you restart SM and redeploy components to unit test them ? All components in ServiceMix have unit tests with a real ServiceMix container embedded, which gives a lot more confidence imho ...
On 3/14/07, jlo_gestalt <[EMAIL PROTECTED]> wrote:
That is how we approached runtime testing by creating a simple BC Service Unit; typically the HTTP BC. We also use http://jakarta.apache.org/commons/httpclient/ Commons HTTP Client to run automated tests in our CI environment. However we use the http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=JBIMockFramework JBI Mock Framework to get unit tests for our Service Engines and Binding Components. It works out really well so we can develop SEs and BCs quickly by not having to restart SM and redeploy components. We can write unit tests and get alot of confidence at that level. carmichs wrote: > > I am in the same spot as you. If you figure it out, please post your > answer. If I figure it out, I will do the same... > > > > > > > > Felipe Gaucho wrote: >> >> ok, hello-world finally is working here.... >> >> my question now is how to test it on ServiceMix runntime ? >> >> I know there is a test case into the component, and when I run "mvn >> install" it works fine ans show the colorado sky on the screen... >> >> then I copied the zip file into service mix and everything looks fine.. >> >> now, how to test it in the running ServiceMix ?? how to send messages >> exchanges to the installed component ? >> > > -- View this message in context: http://www.nabble.com/how-to-test-a-component--tf3362007s12049.html#a9475335 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
