Did you get any problem using “WebUI.verifyElementVisible()” keyword or “WebUI.waitForElementVisible()” keyword? If so, it would be better asking about that incident, rather than talking about the docs.
Why not you share the log, screenshot, HTML sources etc as the following post explains:
As far as I understand it, it is meant to mean actually visible, on screen, in the current viewport of the browser. Perhaps @Brandon_Hein knows more?
For the same reason you have doubts, I wrote my own WaitVisibleToHumans() - but even that has issues. When an element is semi-obscured by a dimmer, it’s considered not visible to humans.
But, back to the question - create a webpage with a super tall div. Place another element beneath it. Test to see if the bottom element is verifiably visible without scrolling. Post back your results (like a good engineer/scientist)
According to the documentation, the keyword uses ExpectedConditions.visibilityOf() to determine visibility, and according to the documentation for ExpectedConditions.visibilityOf():
“Visibility means that the element is not only displayed but also has a height and width that is greater than 0.”
tl;dr I believe it checks the style attribute for display: none, and for height: 0 and width: 0. To Russ’s point, this means that even if you can’t see it with your eyeballs, it may still be considered visible by that definition.
Thank you, Russ_Thomas. I can try to do it when I a have a chance, though I’ve never created a webpage in my life. Still, like a good tester, I’d rather know the EXPECTED behavior. If the bottom element is not verifiably visible without scrolling, it might be that something is wrong with the page under test or with my test (nobody is perfect))
But note also that my approach has the intention of supporting a subsequent click action (or similar). The code actually performs a Web API scrollIntoView(). In other words, it will only fail when all reasonable attempts to reveal it have failed.
Thank you Brandon_Hein. It’s really good to know that ““Visibility means that the element is not only displayed but also has a height and width that is greater than 0.””. Still, I’m not sure whether “visibility” means that an element “actually visible, on screen, in the current viewport of the browser”.
Thank you, Russ_Thomas ( I can see it now )) . Could you please let me know how I can use your function in Katalon ? That might sound like a dumb question but I’m not even a novice to Katalon yet. I’m just a guy who likes it and really want to use it for automation in our company.
Sorry. I realized midway through this discussion I’d led you down a path that required a lot of you - perhaps more than you are prepared for at this stage in your testing “journey”.
Thank you, Russ_Thomas. Sorry, I didn’t make myself clear. What I meant in my previous question was how your (or any) JS function can be used and RE-USED in Katalon? Suppose, your function works (a fair assumption, I guess). Obviously, that it can be included directly in the test script. But what if I need to use it in multiple tests. In my previous experience with Selenium projects I just put all JS scripts in the static functions in one of my util classes and just called those functions when I needed them. What approach should be used in Katalon? Thanks.
Sorry. You DID make yourself clear - my answer didn’t cover all the bases.
Utility functions (methods in Groovy-speak) are created by Custom Keywords. These are merely classes you create and add methods like you mentioned to them which you can call from any test case.
For all the background info, start here:
Once you’ve digested that, understand this: you don’t NEED to make keywords with @Keyword. You only need @Keyword if you want your methods to show up in Manual view. In script view, if you declared your methods as static, you can import them statically and re-use them anywhere:
import static myutils.* // or whatever you called them