The best way to write these tests would be use a test-config that starts with the all configuation but without anything in deploy. You then deploy an ear that includes everything, * a war * an ejb2 * an ejb3 * an mdb * a rar * a datasource * an mbean * a pojo Then you deploy all the files from all/deploy and test the application works. But then you repeat the test, by undeploying all/deploy and then redeploying them in a different permutation. Not only does this test that dependencies are working across all our deployments, it also checks they can be stopped and restarted. e.g. There is a known issue with EJB2 where this fails https://jira.jboss.org/jira/browse/JBAS-5332 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178197#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...