I wonder why Katalon test case turns green although there is a warning “Test object with id ‘Object Repository/’ does not exist”. I expect a test case to stop once a warning event occurs. Windows 8.1/Katalon 7.0.8 I use STOP_ON_FAILURE setting by default.

This is how Failure Handling works: [image] Failure Handling Failure handling settings allow users to decide whether Katalon Studio will continue running or not in case of errors occurs during execution. Currently, Katalon Studio supports the following failure handling... …

I know. But how to make Katalon stop a test case once a warning event occurs?

Typically, “warnings” are not treated as aborts or assertion failures. You can try this: [image] The other possibility is to trap the boolean from one of the verifyElement* APIs and use KeywordUtil. https://docs.katalon.com/javadoc/com/kms/katalon/core/util/KeywordUtil.html https://docs.katalo…

I’ll ask this question another way. What must happen in order to stop a test case containing the following code? WebUI.verifyElementPresent(findTestObject(

@devalex88 @ThanhTo I think this may be a bug. As you’re aware, I don’t run tests like this, so treat this report with due distrust :wink: Tested in Katalon 7.0.8 @anbanbanb Okay, here’s my Project Setting: [image] Here is my script (wam is just my way of writing comments - safe to ignore). …

[image] Russ_Thomas: if(!WebUI.verifyElementPresent(to, 5, FailureHandling.STOP_ON_FAILURE)) { KeywordUtil.markFailedAndStop(“Element not present”) } This works. But I have many lines with checking objects, and it is inconvenient to use three lines of code for verification instead of one. Ar…

[image] anbanbanb: This works. But I have many lines with checking objects, and it is inconvenient to use three lines of code for verification instead of one. That’s the point of the bug report. Sit back and wait for the devs to check it out.

Hi @anbanbanb [image] [WebUI] Verify Element Present Description Verify if the given web element does present on DOM. Parameters Param Param Type Mandatory Description to TestObject Required Represent a web element. timeout int Required System will wait... So as…

[image] ThanhTo: Therefore we adjusted the behavior to match the expectations against the documentation. @ThanhTo @devalex88 @duyluong Guys, keep in mind when you read this, I don’t use these APIs, so it doesn’t really matter to me, but, as someone trying to help others, now I have a problem…

The purpose of Failure Handling is to handle all types of failures, not just the “considered-as-failure” of verifying element presents or exists. There are many exceptions which the implementation of verifyElementPresent may throw that may have nothing to do with the intention of the keyword (i.e Nu…

FailureHandling Change breaks legacy code (was STOP_ON_FAILURE does not stop a test when verifyElementPresent returns false)

Bug Report

Russ_Thomas November 10, 2019, 4:45pm 2

This is how Failure Handling works:

Tests are now false-passing with a broken step

Topic		Replies	Views
Unable to verify IF element present or not Web Testing katalon-studio	18	8171	March 12, 2024
How to check element status in conditional statement? Miscellaneous	6	1710	August 12, 2021
Katalon 7.08 doesn't detect errors Web Testing katalon-studio	11	1456	November 15, 2019
Default keywords related to element checks e.g. verifyElementPresent , returns exception instead of boolean false Web Testing katalon-studio	13	1541	October 22, 2019
Execute if/else when Element exists Web Testing katalon-studio	59	39913	January 17, 2023

FailureHandling Change breaks legacy code (was STOP_ON_FAILURE does not stop a test when verifyElementPresent returns false)

Related topics