Definitely, we just didn't manage to squeeze it into the schedule for this release, which was already way late.. Mocking HTTP Responses currently can be done either with an onRequest script as you have done, or by using the docroot setting in the MockService options dialog for mocking static content. Ultimately there will be another tab in the MockService editor named "Resources" containing a list of MockResources which in turn dispatch to MockHttpResponses.. (or something..), and an accompanying HttpMockResponse TestStep. Any further ideas/suggestions are of course always welcome!
sure.. you could either do this from a groovy script or use the DataSource step in soapUI Pro, which you can set to fail if it does not find any data (so you could parameterize its SQL with data from a previous request/response)..
hmm.. I can't reproduce this straight off.. do you have a more detailed error or stacktrace in the error log maybe? Can you show the exact response message you are asserting? Are you using 2.5 final?
yes, you need to associate your request with the created outgoing wss configuration; you can do this in the "AUT" inspector at the bottom of the request editor.
hmm.. if the WSDL is generated dynamically by the services runtime then probably not; check with the corresponding webservice framework functionality..
You can manually call discard() on TestStepResult objects that you no-longer need, soapUI 2.0.2 will automatically keep all errors so this might be an option (discard after you have reported them..)
yes.. the policy in the WSDL specifies a rather comples WS-Security and WS-Addressing setup which you would have to configure manually in soapUI. Alternatively maybe you can expose the service with the BasicHttpBinding for testing purposes only?
Show Posts
