Forum Discussion

qha000's avatar
qha000
New Contributor
14 years ago

What is the definition of "failed" versus "complete"

I'm new to LoadUI and had question regarding the “failed” queries in the load test. I’m trying to figure out the basis for these failures which is not obviously based on the assertions (such as SOAP Response, XPath Match) I have used in SoapUI. My queries are being sent via LoadUI to an Apache server which are then forwarded to an application in the backend for processing and returning results. Even when the application in the back office is stopped manually, the test runs still complete with no failures. I haven’t used any assertions in LoadUI but it seems like the failures are merely based on transaction time (there must be some default that’s being used perhaps). Any feedback is appreciated.
  • 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
  • qha000's avatar
    qha000
    New Contributor
    Thanks for your quick response Dain. I'm using SoapUI Runner but not getting the same result in LoadUI as I would get running the same test (with assertions) in SoapUI. I used the TableLog but again the test case that fails in SoapUI shows as Completed in the table, any suggestions as how I should go about troubleshooting this? Thanks again for your help.