Our development uses .NET Framework 2.0 with WSE 2.0 SP3. This is not an available option in the QTP Web Services setup. The available ones are .NET Framework 1.1 with WSE 2.0 or .NET Framework 2.0 with WSE 3.0. When I enter the info for the URL, Service and Port and click Next ont he Web Services Wizard, I get an Invalid Service message. Any one know of a workaround, maybe using DP, to hit the web service? Or are there any patches available to address this issue? I can access the pages manually without any errors. One of our testers was able to use SOAPUI and was able to access the services, i.e., send the request and recieve a response. But our primary automation tool is QTP and we would like to get it to work with it.
Thanks for the reply. I have been able to make some progress using the XMLHTTPrequest and SOAP, but it's tedious to add parameters. Also any suggestions on tools for xmldiff? I used the QTP inbuilt xmlutil, but not really happy with the diff output. Also need to do coding for adding, modifying and removing nodes and attributes. There is a tool called XMLDiff, but am unable to figure out how to call it in vbscript, CreateRequest(xmldiffpatch.xmldiffoptions) kind of code doesn't seem to work, get an cannot create object error. Any other help is appreciated.
Thanks for the link. I know of that site from before and was able to use the code from the Web Services without the Add In class. We cannot use the Wizard itself to test Web Services as the application I am testing does not have the QTP supported tool kit. I am looking for code to be able to use the wsdl, so QTP recognises it to be able to access the methods and pass in the parameters for each method. Using HTTPRequest and XMLRequest objects, I can post requests and get responses, but have to create and format the xml request for the method which is very tedious.
We don't have it right now and are checking into licensing etc for it. if it is too expensive, i doubt if it will be approved. The dev team is putting together a project in Visual Studio also integrating MBUnit into it. The QA team will have to learn how to add to it and maintain it. It is all C#.