How to stop test case in catch block

Product Forums Katalon Studio
,
1

Hi,

so my question is if there is any possibility to stop running test case in the catch block without getting another error message.

Now I am simply using this:

WebUI.closeBrowser()
WebUI.navigateToUrl(“www.www.www”)

It works, but the problem is that navigation to URL fails too and in html report of test suite it overrides the message on the top from original error produced in Try block of the code.

By message on the top I mean this:

image
image1431×676 79.3 KB

Any suggestions?

3

So, I’m guessing you have something like this:

try {
  // Test steps
} catch(Exception e) {
  doSomethingWith(e.message)
  writeMyOwnErrorHere()
  STOP_EVERYTHING_NOW()
}

Right?

Yeah, me too.

I think it’s possible but it would mean some Groovy metaprogramming (if it’s at a point where it can be hooked in). But I don’t know if that is possible right there - @kazurayam may know. And if it is, he’ll probably have a solution for us by tomorrow :sunglasses:

4

Oh, wait. Would a finally block help? Something like

boolean errorFlag = false

try {
  // Test steps
} catch(Exception e) {
  errorFlag = true
  doSomethingWith(e.message)
} finally {
  if(errorFlag) {
   // write errormessage and fail the test yourself
  }
}

I don’t think that would work, but it may help move you forward…

5

Yes, looks feasible, but difficult to implement. … multiple layers of Closures passing the reference to the caller object to the delegate property inside the callee. …

Not by tomorrow.

6

I figured it would be a rats nest…

7

Indeed.
Metaprogramming without plan inevitably falls into mess.
I think I should not be metaprogramming-holic too much.

8

Marek_Brychta,

In the original post, you wrote:

What do you mean the original error?

What do you mean “Try block”? I ask this because in the snippet you showed

WebUI.closeBrowser()
WebUI.navigateToUrl("www.www.www")

does not have any try{} block.

So I do not quite understand what you mean by saying “It works, but the problem is …”.

9

We’ve created an issue witch try-catch block: https://github.com/katalon-studio/katalon-studio/issues/79.

Thanks @Russ_Thomas, and @kazurayam

10

duyluong,

does this mean,

  1. that the current behavior of Katalon Studio, according to which the parent test case (containing the callTestCase() command) of a failing child test case creates its own error, is not intended and will be changed?
  2. that in future the error occurring in the child test case (which was called by the callTestCase() command) can also be caught directly in the parent test case?

If this is the case, it would finally be the answer to my feature request here: Catch Root Cause Message for a failed Test Step even outside a Test Case
Besides, that would also make large parts of my code here superfluous: How to Highlight Test object in each and every step

11

I could reproduce this problem. Please have a look at my report at

12
  1. callTestCase will throw StepFailedException or StepErrorException if the child test case (callee) has errors.
    Current: the parent test case (caller) always fails even users catch the right exception.
    Next release: the parent test case should fail if users don’t catch the exception and should pass if uses catch the exception.
  2. Yes. In next releases, users can get the root cause exception of StepFailedException or StepErrorException like the below example:
try {
    WebUI.callTestCase(findTestCase('Callee'), [:], FailureHandling.STOP_ON_FAILURE)
} catch (StepFailedException e) {
	println e.getCause()
}
1 Like
13

Hi guys,

Please let us know if this issue has resolve in v6.0.5 or later

14

Yes, I checked it and found the issue was resolved. See the last section “Fixed? — yes”.

1 Like