Alin Dreghiciu sais: anonymous wrote : | Regarding Pax Exam and Husky these two frameworks are almost the same. And both are working with an remote framework. Remote meaning that the Client Runner and Osgi Framework are running in separate processes. Now, of course that we do not share the same names like Conecor, invoker, bridge but architecture wise is the same. With one diff: we consider that all the tests have to run the osgi container and so we do not have the Bridge part in every test method. In rest, all the things like extender based on manifest headers, injection of bundle context, ... | I would even say that Pax Exam adds more to the table because you can configure the osgi framework use for tests for things like system properties, boot delegation packages, system packages, provisioned bundles, ... IT may be that Husky supports that too but was not obvious from the blog post. | | After all, I do not really care if there are other test frameworks over there beside the split effort. As it looks like we think alike why don't you join us? Pax Exam provides an extension point where you can plug in another test container , beside pax runner based one. Implement that based on JBoss and just have it in the classpath and your pax exam tests will be running in JBoss. | | Actually the collaboration could be batter as we can work on adding support for JBoss in Pax Runner. This will mean that jboss can be easy started and used by pax runner users, directly used in Pax Exam without the need to implement the container explained above, could be used n Eclipse via Pax Runner plugin, ... WDYT? | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261192#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...