Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.
The following page has been changed by KamYee: http://wiki.apache.org/ws/FrontPage/Muse/Muse2%2exConformanceTestingTools ------------------------------------------------------------------------------ The WS-I Organization (http://ws-i.org) has developed and made available the WS-I Interoperability Testing Tools to help developers determine whether their Web Services are conformant with defined WS-I profiles. - We will enhance and extend these testing tools to test for conformance against specification levels implemented in Muse 2.x (WSRF 1.2, WSN 1.3, WSDM 1.1, and WS-MetadataExchange). + These tools test Web service implementations using a non-intrusive, black box approach. We will enhance and extend these testing tools with additional assertion statements and associated code logic to test for conformance against the specification levels implemented in Muse 2.x (WSRF 1.2, WSN 1.3, WSDM 1.1, and WS-MetadataExchange). ( More details on these tools and how they work can be found at http://ws-i.org/deliverables/workinggroup.aspx?wg=testingtools (under "[http://www.ws-i.org/Testing/Specs/AnalyzerFunctionalSpecification_Final_1.1.pdf Analyzer Tool Functional Specification]", "[http://www.ws-i.org/Testing/Specs/MonitorFunctionalSpecification_Final_1.1.pdf Monitor Tool Functional Specification]", and "Interoperability Testing Tools 1.1") and http://www-128.ibm.com/developerworks/webservices/library/ws-wsitest/ ). - These tools test Web service implementations using a non-intrusive, black box approach. The testing infrastructure is made up of two main modules, the Monitor and the Analyzer. + The testing infrastructure is made up of two main modules, the Monitor and the Analyzer. - The Monitor is both a message capture and logging tool. It intercepts the messages and a logger re-formats them and stores them in a message log for later analysis. The monitor is implemented using a man-in-the-middle approach. It intercepts and records the messages, then it forwards to the messages to its final destination. + The Monitor is both a message capture and logging tool. It intercepts the messages and a logger re-formats them and stores them in a message log for later analysis. The monitor is implemented using a man-in-the-middle approach. It intercepts and records the messages, then it forwards to the messages to its final destination. We do not anticipate any changes or enhancements needed to the Monitor component. - The Analyzer is an analysis tool that verifies the conformance of Web Services artifacts to profiles/specifications. It analyzes the messages sent to and from a Web service after these have been captured and stored in the message log by the Monitor. The Analyzer performs its checks based on assertions listed in a Test Assertion Document (TAD). The TAD will be extended to include assertion statements gleaned from the specification implemented in Muse 2.x. + The Analyzer is an analysis tool that verifies the conformance of Web Services artifacts to profiles/specifications. It analyzes the messages sent to and from a Web service after these have been captured and stored in the message log by the Monitor. The Analyzer performs its checks based on assertions listed in a Test Assertion Document (TAD). The TAD will be extended to include assertion statements extracted from the specification implemented in Muse 2.x. The associated code logic that the Analyzer will invoke will also be added to this component. - - (!) Under construction - == Usage/Execution Scenarios == --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
