Forum Discussion

MoriG's avatar
MoriG
New Contributor
9 years ago
Solved

Test complete does not load wsdl from web service, localhost or otherwise.

Hi!   First, thanks for any help!   Issue: I am trying to get Test Complete 10 to load our company's web service.. I click Select (in web service -> Edit) and enter the url address "http://loca...
  • AlexKaras's avatar
    AlexKaras
    9 years ago

    Hi Mori,

     

    Excuse me for the delayed reply...

    Unfortunately, I can confirm that I got the same error as you when I tried to open the wsdl file in TestComplete 11.2.

    When I opened the definitions file you've provided to me in the XML editor, I notices that it has the 'service' node and its value is 'GatewayAPIRest'. This inspred me with the idea that the tested service is not SOAP, but the REST one. Is this my guess correct?

    TestComplete does not provide any support means for REST services (though you may test them using plain http system calls).

    I tried to open the definitions file in the SoapUI tool (http://smartbear.com/product/ready-api/soapui-ng/overview/, http://soapui.org/) as a new REST project. SoapUI created a new project but it was blank and did not contain any method.

    Then, I tried to open the file in the SoapUI as a new SOAP project. Initially, SoapUI failed to import the file because it failed to import schema definitions (from the 'types' node, as it failed to navigate to the 'http://desktop-gqmpjvt:8070/API/' address). After I removed all 'schemaLocation' nodes from the file, SoapUI created a new SOAP project, but without any service as well.

     

    The above makes me think that something is missed in your definitions (wsdl) file. I will try to figure out what is missed, but I am not an expert with the wsdl files structure and this may take some time.

    To speed up the process, I would recommend you a) to talk to your developers and ask them if the provided wsdl file is correct and b) to contact Smartbear Support via the http://support.smartbear.com/message/?prod=TestComplete form and reference this thread and the address with the wsdl file that you sent to me.

    I will appreciate if you update this thread with the results and sorry for not been of much help.

AlexKaras's avatar
AlexKaras
Champion Level 3
9 years ago

Hi Mori,

 

Excuse me for the delayed reply...

Unfortunately, I can confirm that I got the same error as you when I tried to open the wsdl file in TestComplete 11.2.

When I opened the definitions file you've provided to me in the XML editor, I notices that it has the 'service' node and its value is 'GatewayAPIRest'. This inspred me with the idea that the tested service is not SOAP, but the REST one. Is this my guess correct?

TestComplete does not provide any support means for REST services (though you may test them using plain http system calls).

I tried to open the definitions file in the SoapUI tool (http://smartbear.com/product/ready-api/soapui-ng/overview/, http://soapui.org/) as a new REST project. SoapUI created a new project but it was blank and did not contain any method.

Then, I tried to open the file in the SoapUI as a new SOAP project. Initially, SoapUI failed to import the file because it failed to import schema definitions (from the 'types' node, as it failed to navigate to the 'http://desktop-gqmpjvt:8070/API/' address). After I removed all 'schemaLocation' nodes from the file, SoapUI created a new SOAP project, but without any service as well.

 

The above makes me think that something is missed in your definitions (wsdl) file. I will try to figure out what is missed, but I am not an expert with the wsdl files structure and this may take some time.

To speed up the process, I would recommend you a) to talk to your developers and ask them if the provided wsdl file is correct and b) to contact Smartbear Support via the http://support.smartbear.com/message/?prod=TestComplete form and reference this thread and the address with the wsdl file that you sent to me.

I will appreciate if you update this thread with the results and sorry for not been of much help.

  • MoriG's avatar
    MoriG
    New Contributor
    9 years ago

    Hi Alex,

     

    OK, I did some digging on my own and reached a conclusion, albeit not a solution.

     

    1) There is no "binding" in the wsdl, and under the service there are no ports defined, so no services may be reached. creating a wsdl file from the data and "dumping" a "port" area under the service opens it, but still since no bindings exist, no operations are released.

     

    2) The service is indeed a REST and as such, Test Compete's web service does not help as you said.

    I will resort to implementing http requests using MSXML2.ServerXMLHTTP.6.0 as I saw on the web.

     

    Thanks for your tests on the SoapUI, I tried that area aswell but since I do not know it, it failed to give me better understanding.

     

    Thanks again.

     

    Mori