[ebxml-iic] Revised Test Framework v1.0 Specification,with Remote Notification documentation added

[Michael Kass <michael.kass@nist.gov>]

Title: Voting on Deployment Template and Test Framework 1.0

Jaques and all,

 

     The changes below point to additional documentation added to the ebXML Test Framework

specification, describing “remote notification” of a Test Driver of a received message bya Test Service

action.  This is a fundamental function of the test framework necessary for interoperability

testing, and I believe necessary for voting the specification as complete.

 

    I am sending the "diff" file, along with the "merged" version for review.  Please send any

comments to the list regarding these changes.

 

Regards,

Mike    

 

 

Modifications to ebXML Test Framework DRAFT Document, v1.0

 

3.2.2 - Added reference to the "Notify" action for Test Driver to

process a notification message, along with specification that service name

is also sent back with the notification message.

 

3.2.4.2 - Added reference to the Service name and "Notify" action for all Test Service

Actions in Reporting Mode, and specified that the “Receive” interface is used for

local test reporting.

 

4.2.1 - Addded "NotificationURL" as a new configuration parameter for the

Test Driver in both the schema image as well as the schema content

Table

 

7.1.11 - Message Store Schema diagram and content table reflect addition of

reportingAction to messages

 

7.1.12 - Service Specific message payloads -added NotifcationRequest

payload to be processed by Test Driver when a message to the Notify

Action is received.  Content can be from any Test Service Action.

Also modified figure 39 TestServiceMessage schema diagram and

schema content table to reflect this new message payload. 

 

In addition, because MIME message information may not available to a Test Driver in Service Mode, only Manifest reference information (payload MIME Content-ID or Content-Location headers) will accompany any message payloads.

 

8.1.3 - Test Suite document message material description is modified

to reflect that same content model is used to build and query messages,

but that MIME and SOAP content MAY NOT be acessable at application

level, and therefore SHOULD NOT be referenced in message declarations

or queries for the purpose of testing.. only for building messages and

retrieving messages.

 

Appendix C - Test Suite Schema - changes in documentation required changes

in schema

 

Appendix D - Message Store Schema - changes reflect changes in documentation

 

Appendix F - Service-Related Message Schema - Reflects addition of ReportNotifcationRequesst payload addition

test_framework_1.0_diffs_merge.zip