You could try writing a groovy script that checks for the failure condition and if its met, use testRunner.fail().
Let me see what I can figure out. While I'm doing research, what (to you) constitutes the difference between a Failure and an Error?
If you look at my original attached snip, you will see the JUnit html report divided into three columns:
TestCases Failures Errors
1 1 0
Note: failures are anticipated and checked for with assertions while errors are unanticipated.
I consider a failure to be something that I expect ( legal return values for instance ) and something that doesn't affect other testcases than the current one. An error should bring the entire test to a stop, as it's so severe that the reminder of the tests and quality cannot be guaranteed.
In my case , I would like an error if the API is unreachable. It does not make any sense to continue the test if the API is down.
