I always get that error " Element click intercepted exception", and tried to put wait before clicking the object, but it is still the same, this object exists on all pages and almost all of them with same issue
here is the llnk: Community App - Admin Panel
Login y@yopmail.com/Password@1
when running the test , it can’t click 3 dots object of last item, I get the above error
Welcome to our forum. I just want to confirm whether your question is related to Katalon Studio or Katalon TrueTest so that I could move it to the right category?
Do you run with your screen maximized so that you can see the dots without moving the scroll bar? WebUI.maximizeWindow()
If you cannot see the dots without moving the scroll bar, then you will have to move the scroll bar before you can click on them, maybe using: WebUI.clickOffset(findTestObject('scrollbar'), 60, 0)
or some other means.
Do you have something like the below as your pathway to the dots in the last row? id("data")/tbody/tr[last()]/td[last()]/div/button
or //table[@id="data"]/tbody/tr[last()]/td[last()]/div/button
I can see the element without moving the scroll bar, and I added WebUI.maximizeWindow() to maximize the window when running the test, and I get the same error
for the pathway to the element, you mean when clicking inspect? I don’t have like that
If you cannot right click and select “Inspect”, then you should try the F12 key and then click on “Open DevTools”. This can allow you to inspect objects on your browser and create pathways to your objects. If you need assistance, people on this forum can assist.
This is a common issue in Web UI automation, typically it happens when some other web element (that could be visible or NOT) overlaps in some way the element you want to interact first, for example: A Div that dysplay some ads banner, or the common “Accept the cookies first” disclaimer, etc.
My suggestion would be to detect first which element is capturing the click (you can check that digging into the log) and then try to avoid this element in some way. Some times the way i found to avoid this kind of problem was using some JavaScript to remove that element first. (Not the happy solution, but it worked)
It was solved when I created the test case again & found that the XPath of that object in the old case (which was failing with the above error) was incomplete, although I used the recorder, but same object on other modules still have the issue, I am still trying
Thank you