Forum Discussion

electric_Insura's avatar
electric_Insura
Contributor
13 years ago

Content assertions fail, testrunner.status = OK?

Hi,

I just put a couple of content assertions through the GUI into my SOAP request.

As I've done many times before with earlier versions of SoapUI Pro, I want to use 
${=testRunner.results[testRunner.results.size()-1].status}
to indicate an overall pass or fail for that particular request. So if I have four rows in my Excel file, three of which cause one assertion to fail, I want those rows marked as an overall "FAILED."

Some of these assertions fail, but 
${=testRunner.results[testRunner.results.size()-1].status}
returns OK no matter what.

I have the testcase configured to fail if any TestSteps fail.

I've seen 
${=testRunner.results[testRunner.results.size()-1].status}
return "FAILED" when one of my assertions in the Web request step fails. However, those assertions were set up as GroovyScript assertions.

Can anyone shed any light here? Why did this work for me before and not now?

2 Replies

    • makane12's avatar
      makane12
      Frequent Visitor
      11 years ago

      Was there ever a resolution for this question? I'm having the same issue. I have several assertions that fail and the test case status in Soap shows as Failed, but the ${=testRunner.results[testRunner.results.size()-1].status} reports as "OK." Unfortunately due to company data security rules, I am not able to upload my project file.

       

      Thanks!