Why does katalon waits over and above the given timeout limit before failing the Test cases ? I have one test steps which i want to fail if the given element is not present within 10 second but katalon waits for around 90 sec to check the element before failing it . these behavior adding up my total…

well … at least, now you know :smiley: in “WEB”, ofcourse is faster because the interraction between the testing framework (no matter if it is katalon, pure selenium coding in whatever language or whatever else) happens on the same physical machine (except if you use remote runs like in selenium gr…

[MicrosoftTeams-image (21)] other than these which logs will you need ? do you need execution0.log file ?

[image] sumiranraut96: Mobile.verifyElementExist You are complaining about Mobile.verifyElementExist but in the screenshot you show a failure of tap. Something does not match. On the otherside, what is in the screenshot is the time taken for the test step to execute, not for the keyword to …

hmm. I am facing this issue for both tap and verifyElementExist. but thanks for the additional info. will check the time duration after disabling the logs once.

[image] sumiranraut96: will check the time duration after disabling the logs once. that should improve it a bit, but you cannot avoid the extra time for the client/server action. the client (in this case katalon) send whatever action to appium, which execute it on the device, wait for an ans…

@sumiranraut96 You used Mobiel.tap() keyword. The Mobile.tap keyword is naughty recently. There is another discussion, which reported tap is too slow: [image] How to do several taps to open hidden elements Mobile Testing …

Thanks @kazurayam @anon46315158 . Thanks for all the information. I went through few past execution reports and looks like it is more to do with the screenshot logging that happened after the failure. just now i disabled the screenshot logging and it took 11 sec only.

@sumiranraut96 Do you mean, taking a single screenshot after a failure in Mobile UI testing took nearly 90 seconds?

[image] kazurayam: Do you mean, taking a screenshot after failure on mobile took nearly 90 seconds? if that’s the case, somehow make sense for me, due to the above i already explained.

yeah it seems so. Even if i explicitly put the Mobile.takescreenshot() command , that also takes almost more than 1 minute to log the screenshot in the report.

Mobile.verifyElementExist(testobject, 10) waited for 90 seconds — far longer than the specified timeout of 10secs. Why?

Web Testing

kazurayam January 29, 2023, 11:36pm 2

You reported 90secs wait after a failture at Mobile.verifyElementExist(x, 10), but I am not convinced that you are reporting a fact. There could be some other cause of failure and probably you missed it. Please check the execution log again.

Or follow the guideline:

Topic		Replies	Views
Verify Keywords are taking 40+ minutes to execute failure cases in Katalon Studio 7.0 Mobile Testing katalon-studio , mobile-testing	16	4881	October 29, 2019
It Takes Too Long to Tap and Verify Element In Mobile Bug Report katalon-studio , bugs-report	20	4120	October 12, 2021
Timeout for keywords are not working on Mobile Bug Report katalon-studio , bugs-report	4	843	November 2, 2019
Katalon Android execution is so slow Mobile Testing katalon-studio , mobile-testing , android	2	314	March 14, 2024
Execution taking too long time Mobile Testing katalon-studio , mobile-testing	0	528	March 17, 2021

Mobile.verifyElementExist(testobject, 10) waited for 90 seconds — far longer than the specified timeout of 10secs. Why?

Related topics