[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-iic] Call tomorrow Thu 15
Jacques,
Attached is the latest update to the Test Framework document. I have added a few proposals in the spec (particularly the <PutMessage> content). I’ve modified all the schemas and descriptions to reflect our discussion/resolution regarding scripting. My comments for today’s meeting below:
Thanks, Mike
-----Original Message-----
Next call exceptionally tomorrow Thursday 15: Time: Thursday July 15, 2004, 2pm PT Agenda: 1. Update on ETSI tests, 2. Test Framework 1.1
technical: [MIKE] – As we have implemented it here at NIST, the Test Driver first “Mutates” via XSLT the <Declaration> content ( providing such things as Timestamp, ConversationID..etc ), then passes the transformed (mutated) document back to the Test Driver. Based upon <ConfigurationGroup> settings of Transport = HTTP… or SMTP , Envelope = ebXML .. or MIME… or SOAP, the Test Driver takes the mutated document object, and makes calls to its API based upon the assumptions of what transport and envelope have been defined. So if a JMS or WS API is to be used, then they would have to be added as <ConfigurationGroup> types.
[MIKE] – We think that instance ID is better choice, and will change schemas to use that instead.
[MIKE] – I am concerned about modeling <Splits> and <Joins> in the Test Framework execution model with semantic meaning of <Forks> and <Joins> in the BPSS domain. I think that we need a few use cases to define how we will handle the conditional execution based upon test results returned by 3 concurrent transaction Threads.
[MIKE] – We have implemented this, but not yet tested it on real cases. 3. Test Framework 1.1 spec: I think that we can list the features that a Test Framework MUST support to be considered “complete”… and perhaps create subsets of features for various types of testing (e.g. A2A, MS conformance testing, P2P Interop testing). Clearly not all features will be necessary for all types of testing.
I created a WSDL binding for SOAP with attachments for Test Driver/Test Service notification messages. 4. Other? We will need to define additional normative schemas for describing message <Declaration> content for various message envelope types.
Regards, jacques
|
IIC_ebXMLTestFramework_V1.1_07_14_04_final_draft.pdf
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]