Forum Discussion
I hope this fits your use case, here's what I did: I set up a SOAP VirtResponse test step and had it built from an Operation on a wsdl and schema. Using an external client, I ran a test against the listening port with an external client. If my client's SOAPAction matched, the request went through.
If the SOAPAction did not match, my client received an error. I think that meets what you want? The test step virt response will provide an error to the client if the SOAPAction does not match what was selected.
- fsking8 years agoNew Contributor
Hi msiadak, thanks for your response. I think I did exactly the same as you describe, but SoapUI NG doesn't validate for SOAPAction.
What I did was create a new VirtResponse Step, selected the operation and interface, filled the port and path and clicked OK. Next filled the response message.
When running the test with an incorrect SOAPAction, the step still validates and no error is returned to sender.
Is there some setting or property I can change to make my SoapUI NG work the same as yours?
Related Content
- 2 years ago
Recent Discussions
- 4 hours ago
- 5 hours ago