The tests really shouldn't care if the underlying implementation is using JCA or ASF. We just need some tests that test every combination (there aren't that many), i.e.: CMT: tx Required: test message receipt. test message is not acked until onMessage returned test throwing RuntimeException test throwing Checked exception test setRollbackOnly etc tx Not Supported first define what the behaviour should be then do the same tests as tx required and check results conform to defined behaviour BMT: Check that message is acked according to ack mode specified in config, i.e. AUTO_ACK, DUPS_OK. Check that defaults to AUTO_ACK if not specified. use UT to being and commit /rollback tx. do some other transactional operation in the UT (e.g. send to another MDB) Then repeat all the above using MDB on queue, topic with durable and non durable subscripton, selector etc. So this isn't about testing the adapter, AFAIK the adapter tests look pretty thorough. This is about testing MDB functionality, and should be agnostic of the implementation. Then we just run the exact same of tests swapping out the invoker-proxy-binding for either JMSContainerInvoker or JCA inflow, and repeat again for JbossMQ and JBM. Should pass all tests in all 4 configurations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002238#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...