Skip to main content

3 Selenium classes that are not so popular to locate elements

Here we have discussed 3 Selenium classes that are not so popular but that can help you locate elements in Selenium:
- ByIdOrName
- ByChained
- ByAll


1) ByIdOrName - This helps the driver to locate an element either by name or by id. This is present under org.openqa.selenium.support package and to use this we have to call the constructor of the ByIdOrName class and pass the Name or ID. This method tries to find the element using ID first and it waits till the max implicit wait time for the element to locate using ID and if it is not able to find the element with ID then only it tries to locate with the Name.

As soon as the driver finds the element with id, it will not check the element with a name attribute and won't want for max implicit wait time either.

driver.findElement(new ByIdOrName("username")).click();

2) ByChained - This helps the driver to locate the element based on the parent element, and it accepts an unlimited number of locators. This is present under org.openqa.selenium.support.pagefactory package. It finds the elements that are matched by the first argument, then searches their descendants using the second argument, etc.


driver.findElement(new ByChained(By.id("username"), By.tagName("input"))).sendKeys("Hi Dheeraj!");

This class will find all DOM elements that match each of the locators in sequence, e.g.

driver.findElements(new ByChained(by1, by2))

will find all elements that match by2 and appear under an element that matches by1.


3)ByAll - This helps the driver to locate the element based on all the given locators. This class searches for elements matched by all of the By arguments passed.

It tries to find the element using the 1st locator and if the element is not present using that locator then it waits for given implicit wait time and once it reaches the maximum wait time then it tries to find the element using the 2nd locator and this logic goes on until it finds the element, or there are no more locators.

This method follows the fallback strategy.

driver.findElement(new ByAll(By.className("ui-flow"), By.id("Register"))).sendKeys("Please Register here:");

If the first locator fails to locate the UI element on the page, then it uses the Fallback Locator Strategy to locate the UI element using the next locator from the multiple captured locators until all the captured locators fail.



Labels:

Comments

Post a Comment

Popular posts from this blog

How to Unzip files in Selenium (Java)?

1) Using Java (Lengthy way) : Create a utility and use it:>> import java.io.BufferedOutputStream; import org.openqa.selenium.io.Zip; import java.io.File; import java.io.FileInputStream; import java.io.FileOutputStream; import java.io.IOException; import java.util.zip.ZipEntry; import java.util.zip.ZipInputStream;   public class UnzipUtil {     private static final int BUFFER_SIZE = 4096;     public void unzip (String zipFilePath, String destDirectory) throws IOException {         File destDir = new File(destDirectory);         if (!destDir.exists()) {             destDir.mkdir();         }         ZipInputStream zipIn = new ZipInputStream(new FileInputStream(zipFilePath));         ZipEntry entry = zipIn.getNextEntry();         // to iterates over entries in the zip folder         while (en...
Post a Comment
Read more

The use of Verbose attribute in testNG or POM.xml (maven-surefire-plugin)

At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation
Post a Comment
Read more

Encode/Decode the variable/response using Postman itself

We get a lot of use cases where we may have to implement Base64 encoding and/or decoding while building our APIs. And, if you are wondering if it is possible to encode/decode the variable/response using Postman itself or how to encode/decode the token or password in postman and save it in a variable? To Base64 encode/decode, the quickest way is to use JavaScript methods btoa, atob: atob - It turns base64-encoded ASCII data back to binary. btoa - It turns binary data to base64-encoded ASCII. Sample code : var responseBody = pm.response.json(); var parsedPwd = JSON.parse(atob(responseBody.password)); // presuming password is in the payload pm.collectionVariables.set("password", parsedPwd);
Post a Comment
Read more