qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weston M. Price (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3751) Add Unit/System Testing to JCA Component
Date Mon, 19 Mar 2012 14:17:37 GMT

    [ https://issues.apache.org/jira/browse/QPID-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232626#comment-13232626

Weston M. Price commented on QPID-3751:


BTW, there was other, protocol related issues in the tests that warrant exclusion as non of
the JCA tests at this point exercise XA functionality. I will take a look at exactly what
the issue is.
> Add Unit/System Testing to JCA Component
> ----------------------------------------
>                 Key: QPID-3751
>                 URL: https://issues.apache.org/jira/browse/QPID-3751
>             Project: Qpid
>          Issue Type: Improvement
>          Components: JCA
>         Environment: All OS platforms, all JEE supported platforms.
>            Reporter: Weston M. Price
>            Assignee: Weston M. Price
>             Fix For: 0.17
>         Attachments: QPID-3751.patch
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message