Hi,
First off, which runner are you referring to? The WebRunner or the soapUI Runner? The soapUI Runner will succeed or fail just as the soapUI TestCase would, based on assertions, etc.
The WebRunner has a few settings to control what constitutes a failure. The default mode will count any HTTP reply as a success (basically the only requirement is that the target is reachable and returns something). You can set a list of HTTP status codes that should count as failures, for instance 404 or 500.
If you're not getting the expected behavior, you can connect a TableLog Component to the leftmost output terminal of the Runner, which will show you each response in detail, and whether it succeeded or not.
Regards,
Dain
eviware.com
