You could try writing a groovy script that checks for the failure condition and if its met, use testRunner.fail().
There is an option you can set via Test Case where you can make the entire test bed fail if one test step fails. The setting is called "Abord test if an error occurs" and you would have to set it per test case.
Hi msiadak
Thanks for the heads up.
I was aware of this option and no matter whether I ticket it off or on the behavior is still the same.
Same thing goes for the 'Fail Test Case on Error' unfortunately.
In the JUnit html report it still shows as 'failure' instead of 'error' and the TestRunner doesn't quit.
Do you know if there are similar settings elsewhere?
Br
You could try writing a groovy script that checks for the failure condition and if its met, use testRunner.fail().
Hi again
Your input is very much appreciated. I do still have issues though.
I've created this groovy script to make sure that it would fail, but it refuses to be interpreted as an 'error' .. 'failure' is the best thing I can get out of it. I'm puzzled :)
testRunner.testCase.testSuite.project.getTestSuiteList().each
{
it.getTestCaseList().each
{
//Switch the parameter value to 'true' if you need to enable 'Abort on Error' option
it.setFailOnError(false)
}
}
testRunner.fail("Result is not as expected!")
if (somevalue != "expected value") {
throw new Exception("Result is not as expected!")
}
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?
This was indeed the best answer though it didn't fix my problems. Thanks for the input.
Glad we got at least part way there. I'll try to do some more investigating too.
