Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The command driver.findElement(By.xpath("xpath"). click(); is not working in Web driver. Kindly check the below code written in selenium RC and webdriver.

Selenium RC :

public void courselibrary_click() throws Exception {"/ksdlms/");

         selenium.type("name=userID", "asha");

            selenium.type("name=password", "welcome");

            System.out.println("ok ok");

Webdriver :

public void courselibrary_click() throws Exception {
        //driver.switchTo().window("KESDEE Learning Management System.");
        System.out.println("ok ok");
       // driver.implicitly_wait(300);

After login to the application, driver is unable to find an element and throwing exception:

FAILED: courselibrary_click
org.openqa.selenium.NoSuchElementException: Unable to locate element: {"method":"xpath","selector":"html/body/table/tbody/tr/td[2]/table/tbody/tr[2]/td[1]/table/tbody/tr[283]/td[2]/a"}
Command duration or timeout: 44 milliseconds
share|improve this question
Do you mean it works in RC and doesn't in Webdriver? Add snippet of HTML – olyv Jun 20 '14 at 11:07
All Se experts recommend to use id > name > link text > class > xpath. Can you use other, more preferred way to locate your element? – Peter Masiar Jun 20 '14 at 14:00

There are perhaps three reasons why this might fail:

  1. The page hasn't finished loading, so the element isn't there
  2. The page has finished loading, and the page simply doesn't contain the item -- perhaps because you spelled it wrong in the test or the developer spelled it wrong in the code
  3. The page contains embedded frames, and the element you seek is in an embedded frame.

Based on your comments to another anwer, it appears that the problem is 3 - the table was in an embedded frame. If that's the case, you need to switch to the frame before locating the element.

share|improve this answer

XPath locator should begin with //.

So try

share|improve this answer
Tried with Xpath locator "//" also, but it was not working. After using the command driver.switchTo().frame(1); it started working. Thanks – user2787080 Jun 20 '14 at 12:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.