I have line of code below and executed it in Katalon 7.08 and 6.3.4: WebUI.verifyElementNotPresent(findTestObject(‘Object Repository/Register Your Kit/input_Register Your Kit_kitbarcode’), 1, FailureHandling.CONTINUE_ON_FAILURE) Results in Katalon 7.08 - PASS (it is incorrect response because obje…

Hi @nikolai In 7.0.8 does the step verifyElementNotPresent get marked as failed but the whole test still passes, or the test step also passes.

No Thanh, Step verifyElementNotPresent is marked as passed in 7.0.8: invalid Kit from My Account page - 13: verifyElementNotPresent(findTestObject("Object Repository/Register Your Kit/p_Lets get started by entering your barcode"), 1, CONTINUE_ON_FAILURE) and whole test case marked as passed altho…

See also [image] FailureHandling Change breaks legacy code (was STOP_ON_FAILURE does not stop a test when verifyElementPresent returns false) Bugs Report @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 …

Hi @nikolai Please refer to my answer in a similar topic: [image] FailureHandling Change breaks legacy code (was STOP_ON_FAILURE does not stop a test when verifyElementPresent returns false) Bugs Report Hi @anbanbanb So as documented, the behavior of verifyElementPres…

I’ve read both of these threads and I’m now confused a bit by this change in functionality (at least, it seems that way). I had a similar issue where I used “verifyElementPresent” (but with FailureHandling of CONTINUE) on a Test Object and failed to find the object, but it only left a warning and t…

[image] jpotrawski: In your opinion, is this a bug that was introduced? Or a misunderstanding of what I’m expecting this feature to do? Both, in my view. I’m composing a response on the other thread.

I see. Appreciate your response and feedback on this issue. I saw the developer’s post on a workaround that uses “If” conditional and manually marking the test case as failed, but that’s going to introduce so much re-work on my part.

I get it. Fact is, the whole thing was wrong from the start - the old behavior and the new are both poor. But hang in there, the devs are generally good at responding to API issues. (Shout out @devalex88 @ThanhTo )

No not you and your code… [image] jpotrawski: Or are you referring to the initial behavior/design of the FailureHandling parameter? Yes, that. Sorry, I thought that would be obvious.

Joshua, hang in there. It may surprise you to know, that us mods have wicked evil powers - one of which is to be able to read deleted posts :alien::shushing_face: So yes, hang in there, and keep asking questions here on the forum. None of us were born knowing this stuff. The only real difference b…

Katalon 7.08 doesn't detect errors

Web Testing

Russ_Thomas November 11, 2019, 7:17pm 4

Topic		Replies	Views
verifyElementPresent method doesnt return false or stop on failed Web Testing katalon-studio	6	1116	March 9, 2023
FailureHandling Change breaks legacy code (was STOP_ON_FAILURE does not stop a test when verifyElementPresent returns false) Bug Report katalon-studio , bugs-report	40	5736	November 17, 2019
Verify Element Not Present Passing When Element is Present Web Testing katalon-studio	3	1381	November 14, 2019
Unable to verify IF element present or not Web Testing katalon-studio	18	8171	March 12, 2024
verifyElementVisible throws an exception rather than return false; Web Testing katalon-studio	4	1207	December 3, 2019

Katalon 7.08 doesn't detect errors

Related topics