How to use isSupportingCdp method of org.openqa.selenium.ie.InternetExplorerDriverInfo class

Is this a timing issue? Is the element (or the whole page) AJAX-loaded? It's possible that it's not present on the page when you're trying to look for it, WebDriver is often "too fast".

To solve it, is either implicit or explicit wait.

The Implicit Wait way. Because of the implicit wait set, this will try to wait for the element to appear on the page if it is not present right away (which is the case of asynchronous requests) until it times out and throws as usual:

// Sooner, usually right after your driver instance is created.
driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);

// Your method, unchanged.
@Test
public void Appointments() {
    ...
    driver.findElement(By.id("ctl00_Header1_liAppointmentDiary")).doSomethingWithIt();
    ...
}

The Explicit Wait way. This will only wait for this one element to be present on the page when looking for it. Using the ExpectedConditions class, you can wait for different things, too - the element to be visible, clickable etc.:

import static org.openqa.selenium.support.ui.ExpectedConditions.*;

@Test
public void Appointments() {
    ...
    WebDriverWait wait = new WebDriverWait(driver, 10);
    wait.until(presenceOfElementLocated(By.id("ctl00_Header1_liAppointmentDiary")))
        .doSomethingwithIt();
    ...
}

In your settings enable "Launch AVD" and enter the name of the Android Virtual Device you created. This will start the emulator (if it's not already started) whenever you start a test.

Update:

You need to set the AVD capability. Simply add this line to your code capabilities.setCapability("avd","AndroidTestDevice");

Update: The textContent attribute is a better option and supported across the majority of browsers. The differences are explained in detail at this blog post: innerText vs. textContent

As an alternative, the innerText attribute will return the text content of an element which exists in the DOM.

element.getAttribute("innerText")

The isDisplayed() method can sometimes trip over when the element is not really hidden but outside the viewport; getText() returns an empty string for such an element.

You can also bring the element into the viewport by scrolling to it using javascript, as follows:

((JavaScriptExecutor)driver).executeScript("arguments[0].scrollIntoView(true);", element);

and then getText() should return the correct value.

Details on the isDisplayed() method can be found in this SO question:

How does Selenium WebDriver's isDisplayed() method work

I doubt if this is possible in Selenium WebDriver.

Similar posts here:

• Getting text from a node

• Reading text using selenium webdriver(xpath)

So in your case, something like (untested pseudo Java code):

String divText = driver.findElement(By.xpath("//div")).getText();
String labelText = driver.findElement(By.xpath("//div/label")).getText();
divText.replace(labelText, "").trim();

    psdbComponent.clickDocumentLink();
    ArrayList<String> tabs2 = new ArrayList<String> (driver.getWindowHandles());
    driver.switchTo().window(tabs2.get(1));
    driver.close();
    driver.switchTo().window(tabs2.get(0));

This code perfectly worked for me. Try it out. You always need to switch your driver to new tab, before you want to do something on new tab.

 System.setProperty(CHROME_PROPERTY, LINUX_CHROMEDRIVER_PATH); // OS and Browser options
 ChromeOptions options = new ChromeOptions(); // create options instance
 options.addArguments("--headless"); // add an option
 driver = new ChromeDriver(options); // create a driver with the specific options instance

You just need to create a ChromeOptions object in which you need to save the options for your own driver. To add your own options just use this: options.addArguments(); and in the parenthesis insert your option in string mode.

For more details and documentation please also check here: http://chromedriver.chromium.org/capabilities

I think this is going to work.

No, it doesn't do it automatically. Two options you can try:

1. Use WebDriverEventListener that is attachable to a EventFiringWebDriver which you can simply wrap around your usual driver. This will take a screenshot for every Exception thrown by the underlying WebDriver, but not if you fail an assertTrue() check.

   EventFiringWebDriver driver = new EventFiringWebDriver(new InternetExplorerDriver());
   WebDriverEventListener errorListener = new AbstractWebDriverEventListener() {
       @Override
       public void onException(Throwable throwable, WebDriver driver) {
           takeScreenshot("some name");
       }
   };
   driver.register(errorListener);
   

2. If you're using JUnit, use the @Rule and TestRule. This will take a screenshot if the test fails for whatever reason.

   @Rule
   public TestRule testWatcher = new TestWatcher() {
       @Override
       public void failed(Throwable t, Description test) {
           takeScreenshot("some name");
       }
   };
   

The takeScreenshot() method being this in both cases:

public void takeScreenshot(String screenshotName) {
    if (driver instanceof TakesScreenshot) {
        File tempFile = ((TakesScreenshot)driver).getScreenshotAs(OutputType.FILE);
        try {
            FileUtils.copyFile(tempFile, new File("screenshots/" + screenshotName + ".png"));
        } catch (IOException e) {
            // TODO handle exception
        }
    }
}

...where the FileUtils.copyFile() method being the one in Apache Commons IO (which is also shipped with Selenium).

What is happening here is the creation of an anonymous class that inherits from ExpectedCondition. In the body of this class he is then overriding the method apply(...).

Firefox 16 isn't supported in v2.23. You will have to either upgrade to v2.26, or downgrade Firefox.