How to use afterClick method of org.openqa.selenium.support.events.Interface WebDriverListener class

You can increase the timeout by modifying your script command. For instance, to increase the timeout to half an hour:

  - travis_wait 30 mvn package -Dtestng=test.xml

See Mor's answer for a great alternative that doesn't "hang" the build output for 30 minutes.

First of all you need to import the proper drivers into the project/class.

like

import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.ie.InternetExplorerDriver;

etc.

The you need to create new Webdrivers for the broswer you need.

like

WebDriver driver = new FirefoxDriver();
WebDriver driver = new InternetExplorerDriver();
WebDriver driver = new ChromerDriver();

etc for each browser.

NOTE: It is tough to use different browsers/drivers in a single test. Either you may use similar tests for each browser and maintain a test-suite (i.e. use one driver and import in a test and maintain similar test for other browsers) or you can use some config files or excel to pick up which browser you want the test to run. You might like to explore http://htmlunit.sourceforge.net/ for headless testing.

And information about OperaDriver can be found here: - https://github.com/operasoftware/operadriver/

Yes, this is definitely possible. See this:

// Find the outer element.
WebElement outer = driver.findElement(By.anything("whatever"));

// This doesn't work, it searches the whole page for the XPath expression.
WebElement inner = outer.findElement(By.xpath("//some/nasty/xpath"));

// This works! It takes the outer element as root.
WebElement inner = outer.findElement(By.xpath(".//some/nasty/xpath"));

Therefore, if I understood your need well, your XPath expression needs to look like this:

By.xpath("(.//tbody)[" + j + "]//div[text()=\"" + collector + "\"])")

EDIT (Holy cow, that's a lot of HTML and only a small amount of it is actually needed :).)

Now that I caught what you're after, I think you don't need this approach at all. Try this instead:

WebElement row = driver.findElement(By.xpath("id('CollectorQoSPerformanceMetricsgrid')//div[contains(@class,'x-grid3-row x-unselectable-single') and .//u[text()='" + collector + "']]"));

Only the XPath expression:

id('CollectorQoSPerformanceMetricsgrid')
    //div[contains(@class,'x-grid3-row x-unselectable-single')
          and .//u[text()='" + collector + "'] ]

Taken apart:

FIND ELEM WITH ID = 'CollectorQoSPerformanceMetricsgrid'
id('CollectorQoSPerformanceMetricsgrid')
    FIND ALL DIV ELEMS THAT CONTAIN 'x-grid3-row x-unselectable-single' IN @CLASS
    //div[contains(@class,'x-grid3-row x-unselectable-single')
          AND HAVE AN <U> DESCENDANT WITH TEXT EQUAL TO collector VARIABLE
          and .//u[text()='" + collector + "'] ]

This finds you only the single row you need with a single command.

If you rather want to stick with your current solution, try:

String rowsXpath = "id('CollectorQoSPerformanceMetricsgrid')//div[contains(@class, 'x-grid3-row x-unselectable-single')]";
List<WebElement> rows = driver.findElements(By.xpath(rowsXpath));
boolean foundCollector = false;
for(WebElement row : rows) {
    if(!row.findElements(By.xpath(".//u[text()='" + collector + "']")).isEmpty()) {
        foundCollector = true;
        break;
    }
}

I would argue storing the files in the page class itself. Loading from properties file would incur additional overhead or parsing a large file. Maintaining such a file would also be harder, even with a good tool support you would be forced to use CTRL + F more than you should.

Even on a more conceptual level it feels wrong. A good fit for storing in properties files are configurable parameters, and especially the ones that are good candidates to be tweaked in runtime.

Locators don't have this nature. If the benefit you're seeking is declaring in a central place you should instead use dedicated constant class, which will give you much better refactoring options.

With ChromeDriver 2.28 & Selenium 3.3.1, the following works:

final DesiredCapabilities capabilities = DesiredCapabilities.chrome();
final ChromeOptions chromeOptions = new ChromeOptions();
chromeOptions.addArguments("--start-maximized");
Map<String, Object> prefs = new LinkedHashMap<>();
prefs.put("credentials_enable_service", Boolean.valueOf(false));
prefs.put("profile.password_manager_enabled", Boolean.valueOf(false));
chromeOptions.setExperimentalOption("prefs", prefs);
capabilities.setCapability(ChromeOptions.CAPABILITY, chromeOptions);
WebDriver driver = new ChromeDriver(capabilities);

It's not very thoroughly documented, but:

driver.switchTo().alert().sendKeys("Some text");
driver.switchTo().alert().accept();

The Alert interface, the switchTo() method.

private WebDriverTest(String os, String version, String browser) {
 super();
 this.os= os;
 this.version= version;
 this.browser= browser;
}

should be

public WebDriverTest(String os, String version, String browser) {
 super();
 this.os= os;
 this.version= version;
 this.browser= browser;
}

PrimeFaces 4.0 uses its own ajax event handler, you can use the following code:

private static final String JS_JQUERY_DEFINED = "return typeof jQuery != 'undefined';";
private static final String JS_PRIMEFACES_DEFINED = "return typeof PrimeFaces != 'undefined';";
private static final String JS_JQUERY_ACTIVE = "return jQuery.active != 0;";
private static final String JS_PRIMEFACES_QUEUE_NOT_EMPTY = "return !PrimeFaces.ajax.Queue.isEmpty();";

private static final int TIME_OUT_SECONDS=10;
private static final int POLLING_MILLISECONDS=500;

private void waitForJQueryAndPrimeFaces() {
   new FluentWait(driver).withTimeout(TIME_OUT_SECONDS, TimeUnit.SECONDS)
      .pollingEvery(POLLING_MILLISECONDS, TimeUnit.MILLISECONDS)
      .until(new Function < WebDriver, Boolean >() {
         @Override
         public Boolean apply(WebDriver input) {
            boolean ajax = false;
            boolean jQueryDefined = executeBooleanJavascript(input, JS_JQUERY_DEFINED);
            boolean primeFacesDefined = executeBooleanJavascript(input, JS_PRIMEFACES_DEFINED);

            if (jQueryDefined) {
               // jQuery is still active
               ajax |= executeBooleanJavascript(input, JS_JQUERY_ACTIVE);
            }
            if (primeFacesDefined) {
               // PrimeFaces queue isn't empty
               ajax |= executeBooleanJavascript(input, JS_PRIMEFACES_QUEUE_NOT_EMPTY);
            }

            // continue if all ajax request are processed
            return !ajax;
         }
      });
}

private boolean executeBooleanJavascript(WebDriver input, String javascript) {
   return (Boolean) ((JavascriptExecutor) input).executeScript(javascript);
}

The behaviour is intended. Here is how it works -

1. You issue driver.get(B). It triggers the browser to open the webpage and then it doesnt have anything to do with the browser, so it doesnt care whether an alert is open or not.
2. When the page loads, pop-up dialog appears, but nothing happens on your code side or Eclipse.
3. When you try to perform another operation, it interacts with browser and sees an unexpected popup dialog.

Now, the problem occurs that modal dialog closes and still exception occurs, so try the following.

1. Enclose your second operation in a try/catch and handle UnhandledAlertException
2. Inside that catch block, perform, driver -> switch to -> alert -> accept
3. After the catch block, perform the second operation again.