LZhang
17 years agoFrequent 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
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