> [...] got it to work using TestComplete last night. A couple months in the making, [...]
Good to know that you got it working... though... why not to ask at least month ago?.. :)
AlumniHi Jesse,
We are glad to here that you have managed to resolve the issue.
Do you mind sharing the cause of it with us? It may help other community members.
Thanks.
The last thing that was causing issues was this part of the script: (straight from TC documentation)
// Create an XMLHTTP object for sending the SOAP request
XmlHttpRequest = getActiveXObject("MSXML2.XMLHTTP.3.0");
We just needed to update it to:
XmlHttpRequest = getActiveXObject("MSXML2.XMLHTTP");
We also removed the array information as that portion was not necessary for our request.
And the last thing was not using the "code" generated from the web services screen (modified to false values):
function Transaction()
{
var Result;
var TypeFactory;
//Get the type factory for the web service
TypeFactory = WebServices.QA.TypeFactory;
Result = TypeFactory.Transaction;
//Result.item1 = ;
//Result.item2 = ;
return Result;
}
to
RequestObj.item1
RequestObj.item2
Hi,
First of all: yes, I remember that you got things working and thus have no good reason to change something in the existing code. :)
> We just needed to update it to:
Unless there are specific requirements to use exact version of ActiveX component (3.0 in your case), the second version of code seems to be more preferable as it uses the latest version available at the given test computer.
> the last thing was not using the "code" generated from the web services
Actually, I preferred the opposite, to use the helper code provided by TestComplete. However, my projects were not JScript-based and this might be the reason as JScript does not support out parameters and requires some workaround code: https://support.smartbear.com/testcomplete/docs/app-testing/web/services/out-parameters-methods.html
