Forum Discussion

jball's avatar
jball
New Contributor
13 years ago

[Resolved] Updated WSDL has new attributes not available

Hi.

I have a test suite that I created for an earlier iteration of a web service.

The new version has some additional attributes (some are required, but not important for this issue).

I am now pointing the tests to the new version of the WSDL, but the new attributes are not available and I cannot figure out how to make them available short of starting all over.

Any ideas or do you require any additional information?

I am using 4.5.1

Thx

4 Replies

  • Hi,

    Have you updated the WSDL in your project to the new one (using the Refactor Definition action on the interface popup menu)?

    regards,

    /Ole
    SmartBear Software
  • jball's avatar
    jball
    New Contributor
    I tried it after I had updated the defintion, so it was comparing itself to itself. I tried it just by refactoring and that worked fairly well.

    We can consider this issue resolved.

    I do have another question, let me know if you want to post another topic, but is there a single file that I can go in an mass update my assertion teststep? What happened was, the developers changed an arrays name from Items to Item. I was able to map it for the requests using the refactor screens. But I have found that within an Assertion TestStep I need to go into each actual assertion and change

    declare namespace cic='http://schemas.datacontract.org/2004/07/CIC.XYZ.CBO';
    declare namespace tem='http://tempuri.org/';
    //tem:CreateOrder[1]/tem:items[1]/cic:OrderItem[2]/cic:Description[1]

    to
    declare namespace cic='http://schemas.datacontract.org/2004/07/CIC.XYZ.CBO';
    declare namespace tem='http://tempuri.org/';
    //tem:CreateOrder[1]/tem:item[1]/cic:OrderItem[2]/cic:Description[1]

    taking the s from :itemS[1] for about 50 assertions.

    It appears that the actual assertions within the SOAP Requests have converted fine, this is only on Assertion Test Steps.

    If the answer is no, no big deal. I can manually update them.

    Thanks OLE - Top notch response as usual.
  • Hi,

    thanks - this is actually a bug in the refactoring engine - I'll report it internally. For you now you can just open the soapui project xml file in a text editor and do a find-and-replace as desired..

    does that work ok?

    regards!

    /Ole
    SmartBear Software
  • jball's avatar
    jball
    New Contributor
    Yes it does.

    Thanks for the prompt response.