cancel
Showing results for 
Search instead for 
Did you mean: 

Keep existing value for update interface definition and etc

Frequent Contributor

Keep existing value for update interface definition and etc

Hi:

1  When we update interface definition, there are currently four options available:

Create new requests
Recreate requests
recreate optional
create backups

Is it possible to add one more option "keep existing values"?  That way, we don't need to reenter all values for each request and it would be very helpful for us.

2.  Another request is when we update interface definition, shouldn't it be synchronized with all methods/requests (inside test suites) that are referring to that interface?  For example, if there are 50 methods/requests and we use them in 5 test suites, we then need to go into each method request to do a "recreate a default request from the schema."  It's very inefficient.  An update to the definition of the interface should in theory propagate the changes to all referred methods/requests (inside test suites) as well.

3. When we click on "recreate a default request from schema" for a particular request, it updates the XML structure for that request.  But we have no way of knowing what XML elements get added or removed.  Could you add a pop-up windows or display a message in Soap Request windows to indicate what has been changed and the number of changes.  Then we can keep track of all the WSDL changes and that piece of information is very useful for us.

4. Last but not least, does SoapUI have an option of comparing new WSDL with old WSDL?  Maybe you can add an icon to do a side-by-side comparison and highlight the changes for New/Old WSDLs.  Then the user can easily pinpoint the changes and make modifications accordingly.


Hope these make sense to you.

Thank you,
Li
3 REPLIES 3
Super Contributor

Re: Keep existing value for update interface definition and etc

Hi Li,

thanks.. this all makes very much sense.. "WSDL Refactoring" is one of the top major features we are planning for an upcoming release later this year.. which will hopefully cover many of these issues.. Regarding items 1 and 2:

1) Yes, I'll add that right away
2) Yes.. it should be that way now already.. I'll double check..

regards!

/Ole
eviware.com
Frequent Contributor

Re: Keep existing value for update interface definition and etc

Hi:

Thanks for your reply

Item 2 -- an update to the interface definition doesn't propagate changes to all methods/requests in the latest snapshot release version.  Pretty sure about it

Does "WSDL refactoring" take care of item 3 and 4?

Thanks,
Li
Super Contributor

Re: Keep existing value for update interface definition and etc

Hi Li,

hmm.. then I would say it is a bug.. can you attach or mail a project file together with a WSDL that when updated does not update all associated requests?

Regarding 3 and 4.. yes, WSDL Refactoring takes care of all items related to changes to the WSDL and how they should be propagated to requests. Both showing information on the actual changes performed and providing some kind of interactive "WSDL Diff" functionality..

regards!

/Ole
eviware.com
New Here?
Join us and watch the welcome video:
API Testing Mistake #2
APITestingMistake#2
Top Kudoed Authors