qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3751) Add Unit/System Testing to JCA Component
Date Wed, 14 Mar 2012 15:16:40 GMT

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

Robbie Gemmell commented on QPID-3751:

The test only needed to be excluded from the Pre0-10 profiles due to its reliance on 0-10.
It had presumably already passed on the 0-10 java profile.

We really need to get away from the idea that certain things are 'for the C++ broker' or 'for
the Java broker'. There might not have have been extensive(/any) testing performed to certify
the JCA adapters use against the Java broker, but that doesnt necessarily mean it wont work
and being based on a common AMQP 0-10 client it could realistically be expected to do so.
Certainly, automated tests are one way to verify that to some extent if nothing else was done
(another reason I was so keen that it should have unit and system tests originally, beyond
the simple fact that it should have either way) and so any such tests that exist and are passing
should at least be allowed to continue running.
> 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