Hi Tim, what pax-exam-karaf provides in addition to plain pax-exam testing, is that the test is run inside a real karaf container and you don't need to describe how you need the container itself to be provisioned.
On top of that, it allows you to make use of all Karaf services from inside your test, including the features service itself which make provisioning of your application inside the integration test even more easy. In your test you can inject any OSGi service. You don't need to use karaf commands at all if you don't wish. But seeing how the executCommand method is implemented might help you understand how you can reuse OSGi services. I have some additional links to provide with automated itests using pax-exam-karaf: https://github.com/jclouds/jclouds-karaf/tree/master/itests https://svn.apache.org/repos/asf/whirr/trunk/platforms/karaf/itests/ https://github.com/fusesource/fuse/tree/master/fabric/fabric-itests/fabric-pax-exam Again, in those tests you'll see using the commands a lot, but that's more because I was trying to emulate use cases that reproduce bugs etc. Its not mandatory to do so. -- *Ioannis Canellos* * FuseSource <http://fusesource.com> ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
