Currently the JCA component/code lacks any unit testing as well as any integration testing. Further, the necessary configuration isn't in place to allow for this to work as it stand today. Originally we were using our internal TCK in conjunction with the JCA examples to test the adapter. It was initially thought that the requirement of a running application server was a 'must have' and introducing this requirement into the test framework would be too disruptive.
I have had time (finally) to reconsider this. Being that we provide a non-managed (i.e. non JEE) javax.resource.spi.ConnectionManager there is a good amount of unit testing we can do, as we as being able to provide contributions to the system tests. Further, for certain tests that require app server functionality, simple mock objects can be useful. While we only officially support the C++ broker for JCA, this shouldn't impede unit or system testing as the Java broker is sufficient to at least cover a majority of our test cases. For those future tests that actually require the C++ broker we can use the excludes mechanism and address this need at that time.