Solution for the error "Unable to click on object"

[rafiq]

I am using Katalon Studio Record and play to record the test cases but due to some issue when i am trying to play it, it gives me error
com.kms.katalon.core.exception.StepFailedException: Unable to click on object ‘Object Repository/Page_es Grade section codes/button_Close’ (Root cause: com.kms.katalon.core.exception.StepFailedException: Unable to click on object ‘Object Repository/Page_es Grade section codes/button_Close’
Need a fix
I have already tried solutions like waitForElement and delay techniques, as i am new to the automation testing.

[Russ_Thomas]

We need to see the error log where it says “Caused by”.

Read this post - there is a lot of useful information to help you post better reports/questions:

[TIP] How To Help Us Help You!

My test is BROKEN! NOTHING WORKS! HELP ME! Relax. We get it. We really do. There are some pretty smart and clever people on this forum, but you must realize, they are not magicians or wizards or gods. They cannot see your code, they can’t see your errors and they don’t even know what your AUT is meant to do even though it might seem perfectly obvious to you. So please relax and follow the advice below, before you start writing your post. The advice below will tell you the exact information …

[rafiq]

Thanks for you response
The post was also helpful
Here are screen shots of the error.

[Russ_Thomas]

I think you missed this…

@Russ_Thomas

We need to see the error log where it says “Caused by”.

I’m away for most of today - maybe these guys can step in: @Brandon_Hein @kazurayam

[rafiq]

Alright. Here it is.
Caused by: org.openqa.selenium.ElementNotInteractableException: element not interactable
(Session info: chrome=83.0.4103.97)
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘S*******_S***0’, ip: '192.168..*’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, java.version: ‘1.8.0_181’
Driver info: com.kms.katalon.selenium.driver.CChromeDriver
Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 83.0.4103.97, chrome: {chromedriverVersion: 83.0.4103.39 (ccbf011cb2d2b…, userDataDir: C:\Users\EDUBLO~1\AppData\L…}, goog:chromeOptions: {debuggerAddress: localhost:49854}, javascriptEnabled: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: WINDOWS, platformName: WINDOWS, proxy: Proxy(), setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:virtualAuthenticators: true}
Session ID: 3479c26005a76419dea3c41486d7630e

[ThanhTo]

@rafiq

: org.openqa.selenium.ElementNotInteractableException: element not interactable

This suggests the element is not interactable, try to add WaitForElementClickable before clicking the element to see if it helps.

[rafiq]

Thanks Thanh To for the response.
I tried the method waitForElementClickable in the script as
WebUI.waitForElementClickable(‘Object Repository/Page_edublooms Home/button_Close’, 3)
but the result is same.
Caused by: org.openqa.selenium.ElementNotInteractableException: element not interactable
(Session info: chrome=83.0.4103.106)

[Brandon_Hein]

Can you share the locator you are using in test object ‘Page_edublooms Home/button_Close’?

Another possibility is that you may be targeting a different element than the one you were expecting, and that element truly is not interactable.

[rafiq]

The locator i’m using to test is in screen shot.

[Russ_Thomas]

@rafiq

The locator i’m using to test is in screen shot

What Brandon is asking for, is the definition of the test object from Katalon’s Object Repository. Usually XPath, or CSS.

[rafiq]

Oh I see
I think this attachment will do.

[Russ_Thomas]

I don’t use XPath.

If you change the definition to use CSS, this will work:

#UpdateGradeSectionCodes1 .modal-footer button[type=button]

Be sure to WAIT until the button is ready.

[Brandon_Hein]

(//button[@type='button'])[178]

This is a really really bad xpath (I’m assuming it’s from the recorder/object spy).

Try this one instead:

//form[@id='UpdateGradeSectionCodes1']//button[text()='Close']

[helpdesk]

Just a note, that an XPath that should work would be:

id(“UpdateGradeSectionCodes1”)/div[@class=“modal-footer”]/button[@class=“btn btn-secondary”]

Also, if you try to copy and paste the above, you will have to fix “smart” quotes (quotes that have a curl or curve to them) that this forum supports but that KS does not.

[rafiq]

Thanks for taking time to look into my problem, worth appreciation.
I tried all the above solutions you provided but some how I am still facing the same issue. I did some experiment with the xpath as well. But with no luck.
I’m wondering if someone can spear some time so we can fix this problem.
Thanks.

[ThanhTo]

There’s an answer on StackOverflow suggesting it the modal is in another window. It’s not an accepted solution so I am not sure, however it’s worth trying:

Unable to click on a popup button in selenium webdriver with java

You just need to substitute config.driver with DriverFactory.getWebDriver(), the logic should be the same.

[rafiq]

Thanks Thanh To
The post on Stack Overflow suggests to switch to the modal window on which the error appears and also it says to apply wait for element method. I have already used these method
I am stuck here for days now. Better will be to escalate the problem to upper level so that I can set a zoom meeting with them.
Thanks

[pereira.rfc]

@ThanhTo

Unable to click on a popup button in selenium webdriver with java

Hey mate, i’m probably coming late to help, but i had the same problem and i solved it using the function WebUI.enhancedClick(findTestObject(‘Object’)).

Hope it helps someone else in case it won’t help you.

[chaninat]

Is work, Thank alot.