How to use isSupporting method of org.openqa.selenium.safari.SafariDriverInfo class

1) I let Gradle set the system property to the location of the current webdriver files. I need them in my tests, so I set the properties before my test task.

test.doFirst{
    def classpathRoots = project.sourceSets.test.runtimeClasspath.files
    systemProperty 'webdriver.gecko.driver', classpathRoots.find { it.name.startsWith('geckodriver') }
    systemProperty 'webdriver.chrome.driver', classpathRoots.find { it.name.startsWith('chromedriver') }
    systemProperty 'webdriver.edge.driver', classpathRoots.find { it.name.startsWith('microsoftwebdriver') }
}

You must execute JS to set the window.alert call to do nothing. You can use this method.

static void confirmDialog(WebDriver driver) {
    if (driver instanceof PhantomJSDriver) {
        PhantomJSDriver phantom = (PhantomJSDriver) driver;
        phantom.executeScript("window.alert = function(){}");
        phantom.executeScript("window.confirm = function(){return true;}");
    } else driver.switchTo().alert().accept();
}

You can do it by adding Chrome's command line switches "--lang".

Basically, all you need is starting ChromeDriver with an ChromeOption argument --lang=es, see API for details.

The following is a working example of C# code for how to start Chrome in Spanish using Selenium.

ChromeOptions options = new ChromeOptions();
options.addArguments("--lang=es");
ChromeDriver driver = new ChromeDriver(options);

Java code should be pretty much the same (untested). Remember, locale here is in the form language[-country] where language is the 2 letter code from ISO-639.

public WebDriver getDriver(String locale){   
    System.setProperty("webdriver.chrome.driver", "driver/chromedriver.exe");
    ChromeOptions options = new ChromeOptions();
    options.addArguments("--lang=" + locale);
    return new ChromeDriver(options);
}

public void initializeSelenium() throws Exception{
    driver = getDriver("es"); // two letters to represent the locale, or two letters + country
}

YOu can get the source code through svn here it appears:

http://code.google.com/p/selenium/source/checkout

Once you have downloaded that,

In eclipse, find the jar in 'referenced libraries', right click -> properties

enter the location of the src, in the 'Java Source Attachment' edit box.

I found a google groups discussion on the topic. These links look like promising alternative to Browsermob:

• A Selenium CaptureNetworkTraffic Example in Java
• HOWTO: Collect WebDriver HTTP Request and Response Headers
• Automating the Capture of Web Timings with Selenium 2

After some hours I finally found a solution by using Actions without JavascriptExecuter:

Actions actions = new Actions(driver);
actions.moveToElement(website);
actions.click();
actions.sendKeys("Some Name");
actions.build().perform();

Well, it worked for me. However, is this way the better solution ?

First of all, I apologise because I had never worked on a grid before. I thought it will be a frame and will be easier to switch and then scroll to the element using JavascriptExecutor. But, alas! That's not the case for a grid.
And, there must be a table when a grid is involved.

Now, this is what has worked for me.

Note: Do not forget to give some sleep time after each scroll.

I have automated one sample grid, and have attached the sample working code below. Hope this helps in figuring out problem:

import java.io.IOException;

import org.openqa.selenium.By;
import org.openqa.selenium.JavascriptExecutor;
import org.openqa.selenium.Keys;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.firefox.FirefoxDriver;

public class ScrollGrid{

    public static void main(String[] args) throws IOException, InterruptedException{


        WebDriver driver = new FirefoxDriver();
        driver.get("https://demos.devexpress.com/ASPxGridViewDemos/PagingAndScrolling/VirtualPaging.aspx");
        driver.manage().window().maximize();

        //Clicking on an element inside grid to get it into focus
        driver.findElement(By.xpath("//*[@id='ContentHolder_ASPxGridView1_DXMainTable']//td[.='9/30/1994']")).click();

        WebElement ele=null;
        int flag=0;
        int count=0;

        do{
            try{
                //element to search for while scrolling in grid
                ele = driver.findElement(By.xpath("//*[@id='ContentHolder_ASPxGridView1_DXMainTable']//td[.='3/28/1996']"));
                flag=1;
            } catch(Throwable e){
                //scrolling the grid using the grid's xpath
                driver.findElement(By.xpath("//*[@id='ContentHolder_ASPxGridView1']//div[2]")).sendKeys(Keys.PAGE_DOWN);
                Thread.sleep(3000);
            }
        }while((flag==0) || ((++count)==250));

        if(flag==1){
            System.out.println("Element has been found.!!");
        }else{
            System.out.println("Element has not been found.!!");
        }

        highlightElement(driver, ele); //For highlighting the element
        Thread.sleep(5000L); //to check if the element scrolled to is highlighted.
        driver.close();
    }

    //For highlighting the element to be located after scroll
    public static void highlightElement(WebDriver driver, WebElement ele) {
        try
        {
            for (int i = 0; i < 3; i++) 
            {
                JavascriptExecutor js = (JavascriptExecutor) driver;
                js.executeScript("arguments[0].setAttribute('style', arguments[1]);",ele, "color: red; border: 2px solid red;");
            }
        }
        catch(Throwable t)
        {
            System.err.println("Error came : " +t.getMessage());
        }
    }

}

Note: This works correctly now. It will come out of the loop in case the element is found, or if not found after 250 scrolls. '250' is a relative number. You can change it to the number of scrolls you want to perform on the grid.

You can easily ask Selenium to wait until a particular condition is true; in exactly what you have, one alternative would be:

new FluentWait<JavascriptExecutor>(executor) {
  protected RuntimeException timeoutException(
      String message, Throwable lastException) {
    Assert.fail("name was never set");
  }
}.withTimeout(10, SECONDS)
.until(new Predicate<JavascriptExecutor>() {
  public boolean apply(JavascriptExecutor e) {
    return (Boolean)executor.executeScript("return ('Hello' === getName());");
  }
});

However, then you're basically testing exactly what you just coded, and that has the disadvantage that if name were set before you called setName, you haven't necessarily waited setName to finish. One thing I've done in the past for similar things is this:

In my testing library (which replaces real async calls with setTimeout shims), I have this:

window._junit_testid_ = '*none*';
window._junit_async_calls_ = {};
function _setJunitTestid_(testId) {
  window._junit_testid_ = testId;
}
function _setTimeout_(cont, timeout) {
  var callId = Math.random().toString(36).substr(2);
  var testId = window._junit_testid_;
  window._junit_async_calls_[testId] |= {};
  window._junit_async_calls_[testId][callId] = 1;
  window.setTimeout(function(){
    cont();
    delete(window._junit_async_calls_[testId][callId]);
  }, timeout);
}
function _isTestDone_(testId) {
  if (window._junit_async_calls_[testId]) {
    var thing = window._junit_async_calls_[testId];
    for (var prop in thing) {
      if (thing.hasOwnProperty(prop)) return false;
    }
    delete(window._junit_async_calls_[testId]);
  }
  return true;
}

In the rest of my library, I use _setTimeout_ instead of window.setTimeout whenever I need to set something up to happen later. Then, in my selenium test, I do something like this:

// First, this routine is in a library somewhere
public void waitForTest(JavascriptExecutor executor, String testId) {
  new FluentWait<JavascriptExecutor>(executor) {
    protected RuntimeException timeoutException(
        String message, Throwable lastException) {
      Assert.fail(testId + " did not finish async calls");
    }
  }.withTimeout(10, SECONDS)
  .until(new Predicate<JavascriptExecutor>() {
    public boolean apply(JavascriptExecutor e) {
      return (Boolean)executor.executeScript(
          "_isTestDone_('" + testId + "');");
    }
  });
}

// Inside an actual test:
@Test public void serverPingTest() {
  // Do stuff to grab my WebDriver instance
  // Do this before any interaction with the app
  driver.executeScript("_setJunitTestid_('MainAppTest.serverPingTest');");
  // Do other stuff including things that fire off what would be async calls
  // but now call stuff in my testing library instead.
  // ...
  // Now I need to wait for all the async stuff to finish:
  waitForTest(driver, "MainAppTest.serverPingTest");
  // Now query stuff about the app, assert things if needed
}

Note that you can call waitForTest multiple times if needed, any time you need that test to pause until all async operations are finished.

Besides the correct Qwerky's answer, you can also do simple

driver.findElement(By.xpath("//select/option[@value='1']")).click();

This finds the option element with value='1' and clicks it, practically selecting it in the drop-down.

Both mine and Qwerky's solution are described and explained here, in the documentation.