How to use getCanonicalCapabilities method of org.openqa.selenium.edge.EdgeDriverInfo class

Here is how I am sending character by character using Selenium Webdriver (in Java). This way in the back-end, I verify at each letter press if the character exists in the input. Normal element.sendKeys() is not working well for me 2 out of 5 times - the last letter is missing, I guess something is buggy with Selenium Webdriver, I don't know. Try the code below, it works 100% of the time for me.

public void TypeInField(String xpath, String value){
    String val = value; 
    WebElement element = driver.findElement(By.xpath(xpath));
    element.clear();

    for (int i = 0; i < val.length(); i++){
        char c = val.charAt(i);
        String s = new StringBuilder().append(c).toString();
        element.sendKeys(s);
    }       
}

As you see, I get the value needed to be typed and in the for loop, I take each character, convert it to string and send it to textbox. Also, I have a search for xpath, you can change that to id, or classname, or whatever you want.

Yes, all correct.

Here's a screenshot of where to find font-size through Firebug.

Since the ids are supposed to be unique (at least for this page), you don't need findElements to find a list of elements with id by-id and loop through, instead, you use findElement to get the element directly.

try{
        WebElement byId = driver.findElement(By.id("by-id"));

        System.out.println(byId.getTagName());

        System.out.println("get the text for web element with id='by-id' ");
        System.out.println("------------------------------------------------------------");
        System.out.println(byId.getText());
        System.out.println("------------------------------------------------------------");
        System.out.println(byId.getAttribute("id"));
        System.out.println(byId.getCssValue("font-size"));
    }
}

Are you using a standalone server download?

If you download the selenium server package you'll get about 47 jars with it. I believe you need all of those jars in your classpath in order to execute. That package can be downloaded from here

Or the standalone package can be downloaded from http://code.google.com/p/selenium/downloads/detail?name=selenium-server-standalone-2.20.0.jar

If you're not using it right now, the easiest solution might be to switch to the standalone version; otherwise download the full server & add all the jars to your classpath.

You want to specify that like the following:

//td[contains(@class,'deletion') or contains(@class,'addition')]

or

//td[contains(@class,'blob-code blob-code-addition') or contains(@class,'blob-code blob-code-deletion')]

If you want to do a tag independent search then you can simply use

//*[contains(@class,'blob-code blob-code-addition') or contains(@class,'blob-code blob-code-deletion')]

From your answer it looks like you are trying to concatenate two different xpaths

However, contians() is not mandatory here. You also can do without this

//*[(@class='blob-code blob-code-addition') or (@class='blob-code blob-code-deletion')]

One of the differences between Katalon and groovy is that groovy is lightweight as compared to Katalon. Since Katalon offers variety of features in a container, it is easier to use. Scripting is very much encapsulated within it. Groovy on other had provides many features for testing - Do check out Spock (http://spockframework.org) which is mainly used for testing Java/Groovy applications.

In a nut shell; which should be chosen really depends on the team composition of programmers, tech stack on which your app is built, maintainability of the application in scope. Hope it helps...

The simple solution instead of excluding it is to just do

android {
    packagingOptions {
        pickFirst  'META-INF/*'
    }
}

implicitlyWait()

implicitlyWait() is to tell the WebDriver instance i.e. driver to poll the HTML DOM for a certain amount of time when trying to find an element or elements if they are not immediately available. The default wait configuration is set to 0. Once set, the implicit wait is set for the life of the WebDriver object instance.

Your code trial is just perfect as in:

driver.manage().timeouts().implicitlyWait(30, TimeUnit.SECONDS);

Here you will find a detailed discussion in Using implicit wait in selenium

pageLoadTimeout()

pageLoadTimeout() sets the timespan to wait for a page load to be completed before throwing an error.

Your code trial is just perfect as in:

driver.manage().timeouts().pageLoadTimeout(30, TimeUnit.SECONDS);

Here you can find a detailed discussion in pageLoadTimeout in Selenium not working

Note : Try to avoid configuring pageLoadTimeout() until and unless the Test Specification explicitly mentions about the same.

Why WebDriverWait?

Modern browsers uses JavaScript, AJAX and React Native where elements within an webpage are loaded dynamically. So to wait for a specific condition to be met before proceeding for the next line of code Explicit Waits i.e. WebDriverWait is the way to proceed ahead.

Note : As per the official documentation of Explicit and Implicit Waits Do not mix implicit and explicit waits. Doing so can cause unpredictable wait times.

Your code trial is just perfect to wait for the visibility of an element as in:

WebDriverWait wait = new WebDriverWait(driver, 30);
WebElement element = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id(id)));

Here you can find a detailed discussion of Replace implicit wait with explicit wait (selenium webdriver & java)

Your specific questions

• Why is it necessary to assign a WebElement to the following wait : WebDriverWait in conjunction with ExpectedConditions not only returns a WebElement but depending on the ExpectedConditions can return void, Boolean, List too.

• What does WebElement element receive? : As per your code block where you have used ExpectedConditions as visibilityOfElementLocated(), the WebElement will be returned once the element is present on the DOM Tree of the webpage and is visible. Visibility means that the elements are not only displayed but also has a height and width that is greater than 0.

• Is this the right implementation? : Your implementation was near perfect but the last line of code i.e. boolean status = element.isDisplayed(); is redundant as visibilityOfElementLocated() returns the element once the element is visible (i.e. the elements are not only displayed but also has a height and width that is greater than 0).

One workaround is to set the runOrder parameter to alphabetical and then rename your tests to have alphabetical order.

<plugin>
   <groupId>org.apache.maven.plugins</groupId>
   <artifactId>maven-surefire-plugin</artifactId>
   <configuration>
      <runOrder>alphabetical</runOrder>
   </configuration>
</plugin>

This isn't recommended, though - unit tests should be independent of each other. The execution order shouldn't matter.

Go with PhantomJS but if running them in chromedriver is required and you have the resources, this blog has a good recipe on running headless selenium with chrome. Requiring you to download the following...

• VirtualBox
• Vagrant
• NodeJS

If you plan to implement Jenkins or any other CI in the future, I strongly suggest going with PhantomJS though.