Home
Releases
Discussions
Issue Tracker
Source Code
Stats
People
License
RSS RSS Feed

Anyone can upload a patch. Patches are evaluated by project team members and either Applied or Declined.

1-2 of 2Patches < Previous 1 Next >
Status ID Uploaded By Description Work Items Action
Being evaluated
1171 May 4 at
7:34 AM
Data This Patch contains the following providers:

* StopBtsSendPortStep
* CreateBtsSendPortStep
* StartBtsSendGroupStep
* StartBtsReceiveLocationStep
* StartBtsSendPortStep
* StopBtsReceiveLocationStep
* StopBtsSendGroupStep

6108
Download

Being evaluated
124 Jul 9 2007 at
4:17 PM
JohnBundred New web service step and updated xml validation step as requested by Kevin.

New SoapXmlHttpRequestResponseStep - Allows sending of complete soap request envelopes and receiving of complete soap response envelopes. Does not perform any codegen of proxies from schemas which a) overcomes the crash that occurs with included xsd files (i.e. all BizTalk WSE adapter generated web service schemas), b) sends exactly the data in the test case data file rather then the message generated by the proxy, c) provides full control over the request envelope which allows sending of invalid messages scenarios and custom soap header value scenarios, d) allows validation of any part of the soap response envelope. This test step is provided by my colleague Armando Fagundes.

Updated XmlValidationStep - Based on the namespaces in the message to be validated sets up a XmlNamespaceManager. Namespaces with aliases are added with the alias name, e.g. xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" adds the namespace "http://schemas.xmlsoap.org/soap/envelope/" with the alias "soap". Default namespaces are added using the element name they belong to, e.g. <MyElement xmlns="http://www.mydomain.com/mydefaultnamespace/"> adds the namespace "http://www.mydomain.com/mydefaultnamespace/" with an alias of MyElement. This allows much simpler xpath declarations to the used in the validation step rather than the BizTalk style xpaths

e.g. <XPathValidation query="/soap:Envelope/soap:Body/soap:Fault/faultstring">An exception occured</XPathValidation>,

or in the case of an element with a default namespace
<XPathValidation query="/soap:Envelope/soap:Body/MyElement:MyElement/Amount">999</XPathValidation>.

Hopefully business users rather than developers can then define and code the test scenarios.
Download

1-2 of 2Patches < Previous 1 Next >
Updating...