How to get list of found TestObjects

[Andreas_Voit]

My problem is, that at the GUI are two buttons with ident informations. It depends of the screen resolution which button is visible.

I tried to build my test case by using the “WebUI.clickImage” methode. Therefor I made a screenshot of the button and inserted the image at the TestObject settings.

That works very well when manually executing the TestCase or TestSuite. But when I execute it with jenkins over console mode I got the error

com.kms.katalon.core.exception.StepFailedException: Unable to click on image (Root cause: java.lang.Exception: Cannot recognise image on screen)

My next solution is to check which button is visible and only click on that. But I have no idea how to handle this.

I tried to save the result of “findTestObject” in a List, but failed with casting or other errors.

Does anyone has a hint for me?

Thanks

[Russ_Thomas]

@Andreas_Voit

Does anyone has a hint for me?

The best hint I can give you right now, is follow this advice and post back more info:

[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 …

[Brandon_Hein]

In particular, if you can share the HTML for the buttons involved, it would be much easier to provide a solution. The two buttons will almost definitely be uniquely identifiable in the HTML based on resolution.

[Andreas_Voit]

Sorry, sure.

I hope the 2 Screenshots would give you an idea.

The whole site is generated by ext.js.

I wasn’t able to find a difference in the xpath definition.

If you have any solution or idea how to make a difference between the 2 buttons would be great.

Thanks

[Brandon_Hein]

So first, I think that the <span> element that you’ve got highlighted there isn’t really the element you want. You should target the ancestor <a> element instead. Next, I have a couple of questions:

1.) Does an element for both buttons exist in the HTML simultaneously, and only one of them is visible at any given time based on screen resolution? Or do you only ever see one element?

2.) In the above screenshots, are these looking at two different buttons? Or are they screenshots of the same button under different screen resolutions?

Thanks.

[Andreas_Voit]

ad 1: I checked this by using ChroPath and checked it by using following xpath:
//span[starts-with(@id,‘pp-toolbar-create-’) and contains(@id,‘btnWrap’)][count(. | //[@class = ‘x-btn-wrap’]) = count(//[@class = ‘x-btn-wrap’])]

In my opinion, when they are found by xpath, they are in the html code, but only one of them is visible, but both of them are clickable.

ad 2: following Screenshot shows both buttons how they look when they are visible. I merged them into one picture, I hope it’s not too confusing.

Thanks

[Brandon_Hein]

Nice. So notice in the screenshot for ad 1 that one of them has a style attribute, while the other doesn’t. Try adding this as a predicate to your xpath. So it would look something like:

//span[starts-with(@id,‘pp-toolbar-create-’) and contains(@id,‘btnWrap’) and @style]

I’m not sure whether this identifies the non-visible button or the visible one, but in either case, this will make it a unique identifier.

[Andreas_Voit]

wow, that looks great. Now I get the Button 2, which is visible when the resolution is large.

Is it possible to change the xpath to get the button without the style tag?

[Brandon_Hein]

Sure, just negate the predicate:

//span[starts-with(@id,‘pp-toolbar-create-’) and contains(@id,‘btnWrap’) and not(@style)]

[Andreas_Voit]

oh, easy

That works in chroPath, but at execution time in Katalon I get the following error:

Test Cases/Record specific/Create new Record FAILED.
Reason:
com.kms.katalon.core.exception.StepFailedException: Unable to click on object (Root cause: java.lang.IllegalArgumentException: Object is null)
at com.kms.katalon.core.keyword.internal.KeywordMain.stepFailed(KeywordMain.groovy:36)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.stepFailed(WebUIKeywordMain.groovy:65)
at

Have any idea?

[Brandon_Hein]

Did you change the name or location of your Test Object, or the path to it in your test code? That error usually occurs when the Test Object can’t be found at the specified location in the Object Repository.

[Andreas_Voit]

I created a new TestObject with the new xpath value

//span[starts-with(@id,‘pp-toolbar-create-’) and contains(@id,‘btnWrap’) and not(@style)]

and replaced it in the findTestObject-Methode:

old:

WebUI.clickImage(findTestObject(‘Create Record/Create_Button’), FailureHandling.STOP_ON_FAILURE)

new:

WebUI.click(findTestObject(‘Create_Btn’), FailureHandling.STOP_ON_FAILURE)

and now on posting I see, I forgot the folder name “Create Record/”

Now I got error like

Test Cases/Record specific/Create new Record FAILED.
Reason:
com.kms.katalon.core.exception.StepFailedException: Unable to click on object ‘Object Repository/Create Record/Create_Btn’ (Root cause: org.openqa.selenium.ElementNotInteractableException: Element could not be scrolled into view

I tried to focus or scroll to the element
WebUI.focus(findTestObject(‘Create Record/Create_Btn’))
WebUI.scrollToElement(findTestObject(‘Create Record/Create_Btn’), 5)

But it doesn’t work

[Brandon_Hein]

Of course, it can never be easy… That’s a tricky one. I can offer a couple of suggestions:

1.) Try clicking on the element using JavaScript instead of the WebUI API:

WebElement element = WebUiCommonHelper.findWebElement(findTestObject(‘Create Record/Create_Btn’), 30);
WebDriver driver = DriverFactory.getWebDriver();
JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("arguments[0].click();", element);

2.) Try using JavaScript to scroll to the element instead:

// Use code from above, but execute this JS instead:
js.executeScript("arguments[0].scrollIntoView(true);", element);

With this one, you can change the boolean value to true/false in the scrollIntoView() method to try and scroll the element to the top/bottom of the window, respectively.

3.) Try maximizing the browser window before the script tries to click on the button, if you aren’t already. I would try doing this manually first, to see if it makes any difference. Just run the script in debug mode with a breakpoint at the WebUI.click(findTestObject(‘Create Record/Create_Btn’), FailureHandling.STOP_ON_FAILURE) line. If it does work, I can offer you a Desired Capability that will maximize the browser window automatically when the script runs.

[Andreas_Voit]

Thank you so much.

I maximize my browser at the start of the TC.

I found a similar post to my last problem, which includes one of your solutions.

Unable to click on Object, Other Element Would receive click

@HHanh Tran said: Hi there, You can try to click on the element using Javascript instead: - Create a custom keyword and insert script to click on the element using Javascript: https://docs.katalon.com/display/KD/Define+custom+keywords Your custom keyword will be like this: import org.openqa.selenium.WebDriver as WebDriver import org.openqa.selenium.WebElement as WebElement import org.openqa.selenium.interactions.Actions as Actions import com.kms.katalon.core.webui.common.WebUiCommonHel…

I’ll try it tomorrow.

Thank you for your solution to help me to identify the button.

[Andreas_Voit]

Ok, I couldn’t wait till tomorrow.

Your solution

WebElement element = WebUiCommonHelper.findWebElement(findTestObject(‘Create Record/Create_Btn’), 30);
WebDriver driver = DriverFactory.getWebDriver();
JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript(“arguments[0].click();”, element);

helped me and now I’m able to click on this f*** button.

Thanks again, you saved my weekend

[Brandon_Hein]

My pleasure Cheers!

[Russ_Thomas]

@Andreas_Voit

and now I’m able to click on this f*** button.

That’s a very technical phrase only used by fully qualified test engineers and only in the most appropriate circumstances. I guess this is one of those circumstances.