Re: [sca-bindings] JMS test case progress

[Mike Edwards <mike_edwards@uk.ibm.com>]

Folks,

In general, throughout the SCA testcase
suites, I've not created testcases for optional normative statements -
ie those with MAY or SHOULD
keywords in them.  At present,
little can be established when an SCA runtime fails a test for optional
features - after all, it is clearly valid to
not provide the function described.


Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
Email:  mike_edwards@uk.ibm.com

From:	Simon Holdsworth/UK/IBM@IBMGB
To:	sca-bindings@lists.oasis-open.org
Date:	01/06/2010 12:58
Subject:	[sca-bindings] JMS test case progress

---

Folks, 

Here's my report on testcase progress for the JMS test cases:

Testcase framework: 

I've created the skeleton for all the tests following the approach used
by the Assembly testcases.  One issue I had is that the TuscanyRuntimeBridge
for the Assembly tests does not appear to be appropriate for use with JMS
and JNDI, so I have an alternative TuscanyRuntimeBridge implementation.
 It may be worth looking to see if this can be merged with the Assembly
one. 

I also had trouble with the classpath in build.xml getting all the dependencies
working for Tuscany and Active MQ, so I added a build step that collects
all dependent jars - there may be a better way to do that.

For many tests, its necessary to check details of the JMS message exchange
- JMS headers in particular.  So I've created a BaseJMSTestRunner
class, extening BaseJAXWSTestRunner, which uses JMS to send a request and
receive a response, with the message creation, sending and response checking
in separate methods overridden by specific tests. 

At the moment the suite is set up to use Tuscany and ActiveMQ JMS provider.
 Hopefully this is isolated to the build files (pom.xml, build.xml)
and the jndi properties file which controls where the JMS resources are
located (and which JMS provider is used); the test cases are generic JMS
applications. 

Specific testcase comments: 

BJM_3001 (testing "The value of the
@uri attribute MUST have the format defined by the IETF URI Scheme for
Java™ Message Service 1.0 [IETFJMS]")
 I've only done a very simple test using the wrong URI scheme, I've
not done exhaustive testing of the URI syntax. 

BJM_3006 (testing "SCA runtimes MAY
allow other values of the @correlationScheme attribute to indicate other
correlation schemes")  I
don't think there's any way to test this, unless we can provide configuration
that allows a specific SCA runtime to plug in some other supported correlationScheme
value, or indicate that none are supported beyond those defined in the
standard. 

BJM_3010 is the last testcase I've implemented for now.

Regards, Simon 

Simon Holdsworth

---

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU