[ebxml-iic] A couple of things...

MS Interoperability Testing Task Force:
--------------------------------------

As ebXML Messaging Services specification is getting support and committment from a
growing number of companies, the need for testing and maintaining Interoperability
is also growing. 

A specific challenge for the MS ITTF group will be in designing interoperability
tests that are easy to operate, if not fully automated. Indeed, interoperability
cannot be secured once-for-all. B2B messaging systems are dynamic environments: 
they are upgraded like any other system, they rely on third-party software for advanced
services, their configuration may change, and they need also to support changing
modes of communication (CPAs) (and to agree on the precise semantics of these.)
All this is calling for a testing procedure that is easy to set-up and to repeat on a 
periodical basis.

The MS ITTF will have two subteams working in tandem:

1. Test Definition team:

- Will define which Interoperability Test Cases need be done, overall scenarios, 
configuration, logistics and operating options.
- Main objective: come up with a test set that would make sense for the user community.
- Output: an Interoperability Test Suite and scenarios, described in a user-readable way, 
along with operation guidelines, message and MSH configuration material, 
validation rules, etc.

Note: We actually have a lot of expertise on this in member companies of IIC TC. 
(IONA has experience on RosettaNet interoperability testbed and procedures, 
Drummond Group with ebXML MS interoperability testing, and last but not least, 
the participants in previous POC demos who spent long hours debugging interoperability 
between their MSHs.)

2. Test Operation team:

- Will define (a) a format to describe the Test Cases (XML schema, input/output, 
MSH configuration), along with (b) a design of the test driver technology able to 
process these descriptions, execute the tests, generate reports, validate. 
Although implementing the testbed technology is not part of the deliverable, its design 
is paramount to properly define (a), and should also serve as guideline to implementors.
- Main objective: define test format and procedure that can be easily reused/repeated
and largely automated.
- Output: (i) a format to describe the Test Cases, their sequencing, input, output & report, 
(ii) recommendation on how to process these in an automated way (driver design, translation 
of these inputs for MSH, validation of outputs).

Note: It is expected that (2) will share a lot with the work being done currently for 
Conformance Test definitions (Matt McKenzie & Michael Kass & Jacques)

The final Test Cases selected by ITTF will be those agreeable to both teams 
(Definition and Operation), with regard to their respective objectives.