Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Chrome Driver Issue

    Hi,


    I have created a script for Selenium Automation Testing and that's works fine in Firefox with the help of SmartClientFirefoxDriver ,
    But when i am trying to run that script in chrome browser with the help of SmartClientChromeDriver it gives Error.

    In Automated Testing Document it is mentioned that if we want to use chrome then we have to use chrome driver and i am doing respectively but still shows me error.

    The Code is as Follows:-

    By splitBar = ByScLocator.scLocator("scLocator=//HLayout[ID="mainLayout"]/resizeBar[Class=Snapbar||index=0||length=1||classIndex=0||classLength=1]/");
    driver.waitForElementClickable(splitBar);
    driver.click(splitBar);


    Link is working properly as web page is opening & login is also successful but after that the page is taking time to load and then it has to click on the Slider Element , So for that i am using
    waitForElementClickable() but still it shows me Error at driver.click(splitbar).


    The Error is as follows:-

    Starting ChromeDriver 2.20.353145 (343b531d31eeb933ec778dbcf7081628a1396067) on port 1847
    Only local connections are allowed.
    Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: Element is not clickable at point (10, 569). Other element would receive the click: <>
    (Session info: chrome=46.0.2490.86)
    (Driver info: chromedriver=2.20.353145 (343b531d31eeb933ec778dbcf7081628a1396067),platform=Windows NT 10.0 x86_64) (WARNING: The server did not provide any stacktrace information)
    Command duration or timeout: 31 milliseconds
    Build info: version: '2.48.2', revision: '41bccdd', time: '2015-10-09 19:59:12'
    System info: host: 'pranav-laptop', ip: '172.16.123.124', os.name: 'Windows 8.1', os.arch: 'amd64', os.version: '6.3', java.version: '1.7.0_80'
    Session ID: 4ca7db685557b79bd74c7d79fddf42ad
    Driver info: org.openqa.selenium.chrome.ChromeDriver
    Capabilities [{platform=WIN8_1, acceptSslCerts=true, javascriptEnabled=true, browserName=chrome, chrome={userDataDir=C:\Users\abc\AppData\Local\Temp\scoped_dir8736_24396}, rotatable=false, locationContextEnabled=true, mobileEmulationEnabled=false, version=46.0.2490.86, takesHeapSnapshot=true, cssSelectorsEnabled=true, databaseEnabled=false, handlesAlerts=true, browserConnectionEnabled=false, webStorageEnabled=true, nativeEvents=true, hasTouchScreen=false, applicationCacheEnabled=false, takesScreenshot=true}]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:647)
    at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:326)
    at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:84)
    at com.isomorphic.webdriver.SmartClientWebDriver.click(SmartClientWebDriver.java:545)
    at org.test.TestClass.main(TestClass.java:55)


    Why this waitForElementClickable is not working as per expectation in chrome as it is working perfectly in firefox,
    And also why it throw error on line driver.click(splitbar).
    I don't think Sclocator for same Element is different for different Browser!
    So Can you please guide me why i am getting this error and ?
    Last edited by pkothari; 4 Dec 2015, 11:07.

    #2
    So far there's no indication of a failed locator lookup. Instead, it could be that your code is behaving differently in Chrome, such that there really is an element you've placed in front of the splitbar, or that you've got some kind of installation issue with WebDriver.

    There's no way for us to tell because you haven't provided code for the page you're testing. If you suspect this is actually a framework issue, we'll need a sample page with an example of a locator that doesn't work in Chrome.

    Comment

    Working...
    X