bizunit Source Control Rss Feed

Source code checked in, #94877

Project Collection Service Accounts — Mon, 01 Oct 2012 22:38:35 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #94876

Project Collection Service Accounts — Mon, 01 Oct 2012 22:31:06 GMT

Checked in by server upgrade

Patch Uploaded: #10467

fkuiper — Tue, 27 Sep 2011 09:47:32 GMT

fkuiper has uploaded a patch.

Description:
If excuting a non query (like "delete * from [table]") and you set NumberOfRowsExpected = 0. The step will raise an Exception: "System.IndexOutOfRangeException: Cannot find table 0.".
In this fix I've put the test "NumberOfRowsExpected == 0" infront of any other test so this exception will not be raised when NumberOfRowsExpected is set to 0.

Source code checked in, #57274

_TFSSERVICE — Wed, 28 Jul 2010 22:13:23 GMT

Checked in by server upgrade

Patch Uploaded: #2023

Arindrajit — Thu, 30 Oct 2008 15:48:06 GMT

Arindrajit has uploaded a patch.

Description:
Added support for multiple machine in EventLogCheckStep. This is very useful in a clustered or test covering more than one machine. Simply pass machine name in comma separated string like "machine1,machine2,machine3".

Patch Uploaded

Data — Sun, 04 May 2008 07:34:59 GMT

Data has uploaded a patch.

Description:
This Patch contains the following providers:

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

Patch Uploaded

JohnBundred — Mon, 09 Jul 2007 16:17:02 GMT

JohnBundred has uploaded a patch.

Description:
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.

Source code checked in

kevinsmi — Sat, 12 May 2007 21:59:39 GMT

Source code checked in

kevinsmi — Sat, 12 May 2007 21:52:33 GMT