In protractor, browser.isElementPresent vs element.isPresent vs element.isElementPresent

by

All function in a similar way with subtle differences. Here are few differences that i found –

elm.isPresent() –

  1. Is an extension of ElementFinder and so waits for Angular to settle on page before executing any action.
  2. It works when elm is an element(locator) or ElementFinder and not ElementArrayFinder. If multiple elements are returned using the locator specified then first element is checked if it isEnabled() in the DOM. Doesn’t take any parameter as input.
  3. Works best with Angular pages and Angular elements.
  4. First preference to use whenever there is a need to find if an element is present.

elm.isElementPresent(subLoc) – (When there is a sub locator to elm)

  1. Is an extension of ElementFinder and so waits for Angular to settle on page before executing any action.
  2. Used to check the presence of elements that are sub elements of a parent. It takes a sub locator to the parent elm as a parameter. (only difference between this and the elm.isPresent())
  3. Works best with Angular pages and Angular elements.
  4. First preference to use whenever there is a need to check if a sub element of a parent is present.

browser.isElementPresent(element || Locator) –

  1. Is an implementation of webdriver and so doesn’t wait for angular to settle.
  2. Takes a locator or an element as a parameter and uses the first result if multiple elements are located using the same locator.
  3. Best used with Non-Angular pages.
  4. First preference to use when testing on non-angular pages.

All of the above checks for the presence of an element in DOM and return a boolean result. Though angular and non-angular features doesn’t affect the usage of these methods, but there’s an added advantage when the method waits for angular to settle by default and helps avoid errors in case of angular like element not found or state element reference exceptions, etc…

More Related Contents:

  1. Using cross-platform keyboard shortcuts in end-to-end testing
  2. Ways to deal with #document under iframe
  3. WebDriver click() vs JavaScript click()
  4. Element not visible error (not able to click an element)
  5. Understanding execute async script in Selenium
  6. Custom browser actions in Protractor
  7. Take elements while a condition evaluates to true (extending ElementArrayFinder)
  8. org.openqa.selenium.ElementNotInteractableException: Element is not reachable by keyboard: while sending text to FirstName field in Facebook
  9. Is there a way to get element by XPath using JavaScript in Selenium WebDriver?
  10. Execute JavaScript using Selenium WebDriver in C#
  11. Getting the return value of Javascript code in Selenium
  12. Protractor e2e test case for downloading pdf file
  13. What is browser.ignoreSynchronization in protractor?
  14. How can I use command line arguments in Angularjs Protractor?
  15. Unable to sign into google with selenium automation because of “This browser or app may not be secure.”
  16. Selenium Datepicker using JavascriptExecutor
  17. Scrolling to top of the page in Python using Selenium
  18. How to set default browser window size in Protractor/WebdriverJS
  19. Set value of input instead of sendKeys() – Selenium WebDriver nodejs
  20. Non-angular page opened after a click
  21. What does arguments[0] and arguments[1] mean when using executeScript method from JavascriptExecutor interface through Selenium WebDriver?
  22. Accessing elements in the shadow DOM
  23. An error has occured in ‘site url’: Uncaught TypeError: Cannot read property ‘getColomnSet’ of undefined with Selenium and Python
  24. What is JavaScriptExecutor in Selenium?
  25. Reading JavaScript variables using Selenium WebDriver
  26. scrollIntoView vs moveToElement
  27. Mocking and Stubbing with protractor
  28. Opening a new tab using Ctrl + click combination in Selenium Webdriver
  29. Disable images in Selenium Python
  30. Protractor: Scroll down

Leave a Comment