Reputation: 13
I have a soap ui test case that fires off a soap request in one test step and then initiates a mock in the second. The problem is that the target service called in step 1 responds too quickly, ie. before the mock is stood up by soap ui's Jetty. So that target service now receives and HTML page instead of a soap message, which I can't handle. Any way to get soap ui to respond with a soap fault instead of an HTML page?
Upvotes: 1
Views: 1274
Reputation: 1855
Execution in soapUI is sequential and the second step will be executed only when the first one is successful, so putting the mock service code in the second step is the wrong way to do this. The mock service can be started up in the setup script of the test suite or just manually start the mock service before starting execution.
Upvotes: 1