Web Service Mocking feature - feedback needed!
Dear fellow forum members,
I just started playing with soapUI and reading the documentation, but unfortunately, I've been given too little time to evaluate the tool, and so need to take an urgent shortcut: ask for feedback.
We need a tool that would provide a "mock" web service for a client application to consume as if it were the real thing - to be used by both developers and QA. The high-level requirements for the tool are as follows:
* Generate and return XML based on uploaded WSDL/XSD - looks like soapUI can do that, but values need to be populated manually or through script
* Allow users to customize the XML responses, choose when to return which response, and be able to do so based on user's NT login
* Support response "sequencing" to allow users to move from screen to screen within the consuming application while calling the mock services
* Support positive, negative, destructive testing
* Ideally, have the tool run at one central location
Given the above, do you think soapUI would be a good fit? How hard is it to customize - for developers, as well as the somewhat less technical QA folks?
Many thanks for any and all feedback and advice!
jinnantonyx.
I just started playing with soapUI and reading the documentation, but unfortunately, I've been given too little time to evaluate the tool, and so need to take an urgent shortcut: ask for feedback.
We need a tool that would provide a "mock" web service for a client application to consume as if it were the real thing - to be used by both developers and QA. The high-level requirements for the tool are as follows:
* Generate and return XML based on uploaded WSDL/XSD - looks like soapUI can do that, but values need to be populated manually or through script
* Allow users to customize the XML responses, choose when to return which response, and be able to do so based on user's NT login
* Support response "sequencing" to allow users to move from screen to screen within the consuming application while calling the mock services
* Support positive, negative, destructive testing
* Ideally, have the tool run at one central location
Given the above, do you think soapUI would be a good fit? How hard is it to customize - for developers, as well as the somewhat less technical QA folks?
Many thanks for any and all feedback and advice!
jinnantonyx.