Is there any option to disable retry failed test step

Katalon is immediately rerunning failed test steps/Test Suite multiple times and goes in a loop 3-4 times wasting hours instead of failing and stopping. Is there any way to disable it.

image

IN test suite make the – Retry failed execution immediately as 0, by default when you create a new suite it comes with 3 retry. SO make it 0.

set Retry failed execution immediately to 0 in the Test Suite execution settings. By default, new suites can have retries enabled, which makes Katalon rerun failed steps or cases multiple times before continuing.

What to change

In your Test Suite:

  • Open Execution Information.

  • Find Retry failed execution immediately.

  • Set it to 0.

Why this happens

Katalon can be configured to rerun failed test cases immediately, and that can look like it is “looping” over the same failure several times. If that setting is left above zero, the same test case may be retried before the suite moves on.

Also check suite retry settings

There is a separate retry option after the suite finishes:

  • Retry after executing all

  • Set that to 0 too if you do not want any rerun behavior.

Did you try ?

yes it worked.Thanks a lot.

can someone also advise why the failed test steps are taking endless time to get failed and keep waiting.At last i had to stop the script.

it should not take so long, unless you have some activities/steps going within your Custom Keyword common.Actions.Click() .

The screenshot you disclosed shows that the steps of click(findTestObject("Policy/Navigation/btn... failed after 30 seconds.

This indicates that the TestObject “Policy/Navigation/btn…” does NOT point any HTML element in the target web page. Possibly the locator of the TestObject is wrong. How? Why? — I don’t know. Only you can look into your system and find an answer.

If you want others to help you, you need to disclose more information.

The click statement failed after 30 seconds because the Project Settings > Execution > WebUI has the "Default wait for element timeout (in seconds)" has the value of 30.

You can shorten the timeout value; e.g, 10 or 5. Your test steps will still fail but far quicker than the current setting.