All I'm looking for a yes or no answer and a simple example. I'm in the process of putting together a proposal. I'd prefer to stay with SoapUI as it has a lot of useful features and both QA people on the project currently have familiarity with it. Our other choices would be JUnit, XMLUnit (using Eclipse), QTP with web service addon or a combination of solutions. It looks like I have the ability to create classes and I can also create requests dynamically.
http://www.soapui.org/userguide/scripti ... pt_Libraryhttp://www.soapui.org/apidocs/com/eviwa ... ation.html What I envision is creating a class for each API. Within the class have a method that builds the soap request and assertion. Then change the teststeps to a groovy step. This groovy step would creates this request and asserts the actual vs the expected. With the API changing dramatically in the next version and possibly quite a bit in the version after that, I want to cut down on maintenance of the testcases.
Is what I want to do feasible?
Thanks,
Mary
