Forum Discussion

MichaelMcFarlan's avatar
MichaelMcFarlan
Contributor
14 years ago

Starting with SOAP - TestComplete doesn't like WSDL

I'm trying to set up a web service test using Test Complete but I'm having troubles starting. The SOAP service is out on our company website, accessed through port 8090. I specify the location of the WSDL document as <address>:8090. However, all I get is an error saying that there are no services or that the document is invalid.



Does anyone know why this might be happening? I'm new to web testing and soap so don't make too many assumptions about what I know.

8 Replies

  • Julia_K's avatar
    Julia_K
    Icon for Alumni rankAlumni
    14 years ago

    Hello Michael,


    Could you please check whether you can open your WSDL document in a web browser if you specify the document's address in the same way you do this in TestComplete - <address>:8090?


    Also, please check whether the same error occurs if you omit the port number when specifying your WSDL document address in TestComplete.

    Thanks in advance.

  • sonudavidson's avatar
    sonudavidson
    Occasional Contributor
    14 years ago
    how do I need to use the type factory of 


    • ArrayOfStringOfAnyType

    • ArrayOfIntOfanyType 





    Thank You,

    Davidson.
  • Julia_K's avatar
    Julia_K
    Icon for Alumni rankAlumni
    14 years ago

    Hello Sonu,


    Could you please explain what information you need exactly?

    If you want to know how to get access to types declared in your WSDL document via the TypeFactory property in TestComplete tests, please go through the WebServiceInfo.TypeFactory Help topic.


    Thank you.

  • sonudavidson's avatar
    sonudavidson
    Occasional Contributor
    14 years ago
    Hi Julia ,



    Thank you for your reply..



    I came to know how to use type factory.



    Now I'm stuck with one more issue.



    When I try to post request using methods that are displayed under my webservice. I'm not getting any service error from the server nor the request is logged, My Test complete is not resuming. It just stays in PlayBack state..



    I cannot access the application..



    What might be the issue..?? Do you have any idea..??



    Please help me..



    Thanks,

    Sonu Davidson.
  • sonudavidson's avatar
    sonudavidson
    Occasional Contributor
    14 years ago
    Hi Julia ,



    Thank you for your reply..



    I came to know how to use type factory.



    Now I'm stuck with one more issue.



    When I try to post request using methods that are displayed under my webservice. I'm not getting any service error from the server nor the request is logged, My Test complete is not resuming. It just stays in PlayBack state..



    I cannot access the application..



    What might be the issue..?? Do you have any idea..??



    Please help me..



    Thanks,

    Sonu Davidson.
  • Julia_K's avatar
    Julia_K
    Icon for Alumni rankAlumni
    14 years ago

    Hello Sonu,


    When I try to post request using methods that are displayed under my webservice. I'm not getting any service error from the server nor the request is logged, My Test complete is not resuming. It just stays in PlayBack state.


    Does TestComplete stop responding and freeze?


    Could you please check whether the same issue occurs if you disable the debugger in TestComplete? To disable the debugger, you need to disable the Enable Debugging item in TestComplete's Debug menu.


    Also, cloud you please send our Support Team TestComplete's dump files? This will help us to investigate your issue.

    To send the dump files, please follow the steps below:

    1. Download the Debugging Tools for Windows package and install it.

    2. When TestComplete freezes in the playback state, open the Start | Run dialog and execute the following command:

    "C:\Program Files\Debugging Tools for Windows\windbg.exe" -pn TestComplete.exe -Q -pd -c ".dump /m C:\Dump1.dmp;q"


    This command will make WinDbg write a memory dump of the TestComplete.exe process to the "C:\Dump1.dmp" dump file. After the dump is written, WinDbg will be closed.

    3. Correct the dump file name in the above command line (for example, change it to Dump2.dmp), wait for two minutes and execute the command again.

    4. Repeat step 3.

    5. Use the Contact Support web form to send all the generated dump files to our Support Team.


    Thanks in advance.

  • sonudavidson's avatar
    sonudavidson
    Occasional Contributor
    14 years ago
    Hi Julia,



    Thanks for the support...

    I've posted my dumps... 

    Do you have any idea of what might be the reason..??









    Regards,

    Sonu Davidson.
  • Julia_K's avatar
    Julia_K
    Icon for Alumni rankAlumni
    14 years ago

    Hello Sonu,


    Thank you for the dump files. Our developers are currently investigating the issue.

    Our Support Team will contact you via e-mail as soon as any investigation results are available.


    Good luck.