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 Wed, 14 Mar 2012 15:46:40 GMT

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

Weston M. Price commented on QPID-3751:

Hi Robbie,
  I agree in principal and if it were only 0.10 we were talking about, I don't think there
would be an issue. The problem was I forgot to exclude the tests from the 0.9x profile so
this was my failing. The tests that are included do indeed work with the 0.10 profile against
the Java broker but in the interim, because of the disruption to you and your team, we wanted
to unblock you as quickly as possible. 

As Rajith mentioned, JCA makes heavy use of XA, but I don't see this as being an impediment
to most testing efforts. If XA is indeed involved, then we can simply exclude on a test by
test basis.

> 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.15
>         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