cancel
Showing results for 
Search instead for 
Did you mean: 

failOnError versus failTestCaseOnErrors

Highlighted
Occasional Contributor

failOnError versus failTestCaseOnErrors

SoapUI Pro 1.8.0 has these two TestCase Options which sound like they do the same thing:

 

Abort on Error: "Abort test if an error occurs"

Fail Test Case on Error: "Fail TestCase if it has failed TestSteps"

 

I assume the former Aborts the test case if some unexpected internal error occurs (which invalidates the test and for which no assertions would have been defined), whereas the latter Fails the test case if one of the test steps fails in a normal way (e.g. assertion failure).  Is that the case?

 

Related question: what is the difference between a test that Aborts and a test that Fails?  Is the distinction only detectable at the level of Groovy code inspecting the status of some object?  E.g. WsdlTestCaseRunner has methods isCanceled and isFailed but no mention of isAborted.

 

Please clarify.  Thanks.

3 REPLIES 3
Highlighted
Super Contributor

@RBlack

Below is the link to the documentation and that should clear up the differences

https://support.smartbear.com/readyapi/docs/soapui/ui/case.html

 

 

You like the reply. How to give a Kudos / Accept as solution?

 

 

Highlighted
Occasional Contributor

Thanks for the link, though I find the explanation on that page a bit confusing:

https://support.smartbear.com/readyapi/docs/soapui/ui/case.html

 

Abort on ErrorStops the test run when a test step fails.
Fail Test Case on ErrorMarks the test case as failed if a test step fails.
Note:This option does not stop the test run.

 

Although Abort on Error immediately stops execution of a specific test case upon an error, I know that SoapUI will continue executing subsequent test cases (i.e. that setting doesn't stop the overall project run).  

 

In contrast, it seems "Fail Test Case on Error" just means that the test case will be marked as failed because a test step failed, but it keeps executing steps after the failed one.  

 

So it seems that Fail refers to the final status of the test case but Abort refers to whether it continues executing.

 

What would happen if Abort on Error was TRUE but Fail Test Case on Error was FALSE?  If a test step failed, what status would the test case have once it aborted?  

Highlighted
Super Contributor

Honestly I think the second option that is mark test as failure makes no sense to me.

If it fails just mark it as failed.

if its set to False, I would not expect the test to be marked as Fail

all its doing is creating confusion

New Here?
Join us and watch the welcome video:
Announcements
TechCorner Leaderboard
Want a fun and easy way to learn ReadyAPI and show off your skills? Try solving weekly TechCorner challenges and get into the Leaderboard!


Challenge Status

Get a full Raw JMS request

Participate!

Compare an expected JSON value and actual response in Events

Participate!

Fetch value/data from JSON response using Groovy Script

See replies!

Get data from Petstore and add it to Excel sheets

Participate!
Top Kudoed Authors