org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'












60














Sendkeys not working. Please help me to resolve this..



WebElement username = driver.findElement(By.xpath("//*[@id='username']"));      
username.sendKeys("123456");


Console:



Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'

(Session info: chrome=65.0.3325.31)
(Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86)
(WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds

Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'
System info: host: 'NEW-PC', ip: '192.168.0.103', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.8.0_161'


Driver info:



org.openqa.selenium.chrome.ChromeDriver

Capabilities {acceptSslCerts: true, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 2.33.506120 (e3e53437346286..., userDataDir: C:UsersNEWAppDataLocal...}, cssSelectorsEnabled: true, databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: XP, platformName: XP, rotatable: false, setWindowRect: true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: , version: 65.0.3325.31, webStorageEnabled: true}









share|improve this question





























    60














    Sendkeys not working. Please help me to resolve this..



    WebElement username = driver.findElement(By.xpath("//*[@id='username']"));      
    username.sendKeys("123456");


    Console:



    Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'

    (Session info: chrome=65.0.3325.31)
    (Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86)
    (WARNING: The server did not provide any stacktrace information)
    Command duration or timeout: 0 milliseconds

    Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'
    System info: host: 'NEW-PC', ip: '192.168.0.103', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.8.0_161'


    Driver info:



    org.openqa.selenium.chrome.ChromeDriver

    Capabilities {acceptSslCerts: true, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 2.33.506120 (e3e53437346286..., userDataDir: C:UsersNEWAppDataLocal...}, cssSelectorsEnabled: true, databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: XP, platformName: XP, rotatable: false, setWindowRect: true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: , version: 65.0.3325.31, webStorageEnabled: true}









    share|improve this question



























      60












      60








      60


      4





      Sendkeys not working. Please help me to resolve this..



      WebElement username = driver.findElement(By.xpath("//*[@id='username']"));      
      username.sendKeys("123456");


      Console:



      Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'

      (Session info: chrome=65.0.3325.31)
      (Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86)
      (WARNING: The server did not provide any stacktrace information)
      Command duration or timeout: 0 milliseconds

      Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'
      System info: host: 'NEW-PC', ip: '192.168.0.103', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.8.0_161'


      Driver info:



      org.openqa.selenium.chrome.ChromeDriver

      Capabilities {acceptSslCerts: true, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 2.33.506120 (e3e53437346286..., userDataDir: C:UsersNEWAppDataLocal...}, cssSelectorsEnabled: true, databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: XP, platformName: XP, rotatable: false, setWindowRect: true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: , version: 65.0.3325.31, webStorageEnabled: true}









      share|improve this question















      Sendkeys not working. Please help me to resolve this..



      WebElement username = driver.findElement(By.xpath("//*[@id='username']"));      
      username.sendKeys("123456");


      Console:



      Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'

      (Session info: chrome=65.0.3325.31)
      (Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86)
      (WARNING: The server did not provide any stacktrace information)
      Command duration or timeout: 0 milliseconds

      Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'
      System info: host: 'NEW-PC', ip: '192.168.0.103', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.8.0_161'


      Driver info:



      org.openqa.selenium.chrome.ChromeDriver

      Capabilities {acceptSslCerts: true, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 2.33.506120 (e3e53437346286..., userDataDir: C:UsersNEWAppDataLocal...}, cssSelectorsEnabled: true, databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: XP, platformName: XP, rotatable: false, setWindowRect: true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: , version: 65.0.3325.31, webStorageEnabled: true}






      java google-chrome selenium selenium-webdriver selenium-chromedriver






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 27 at 12:46









      DebanjanB

      37.9k73375




      37.9k73375










      asked Feb 4 at 14:23









      maharaja

      306135




      306135
























          7 Answers
          7






          active

          oldest

          votes


















          105














          I was seeing the same issue. The problem only appears when using Chrome 65 (currently: dev channel). With Chrome 64 (both stable channel and beta channel) everything worked fine.



          It turns out I had an old chromedriver installed. Specifically, I was using chrome=65.0.3325.51 with chromedriver=2.29.461585. Running npm install -g chromedriver bumped chromedriver to 2.35.528157 and now the problem is solved. Hope this helps!



          TL;DR: run npm install -g chromedriver






          share|improve this answer



















          • 2




            Thanks! It worked. Updated the chrome driver to 2.35
            – maharaja
            Feb 8 at 17:37










          • You're welcome. If the answer solves your problem, it's customary to mark it as "accepted answer".
            – Martijn
            Feb 8 at 21:39






          • 2




            chromedriver v2.35 supports chrome 62-64 at the moment
            – Anton
            Feb 26 at 16:13










          • I updated this to 2.38.0, But when I check the version, it always says 2.33. I have changed the package.config (Visual Studio C#)...I cannot find any reference to 2.33 anymore. Where could this be? I tried to delete the project and recreate it.I am using the standalone selenium server..
            – Greg P
            Apr 23 at 12:25










          • my chromedriver didn't automatically update in katalon studio. why is this and what can I do about it?
            – user74843
            May 25 at 14:41



















          15














          The error says it all :



          Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'

          (Session info: chrome=65.0.3325.31)
          (Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86)
          (WARNING: The server did not provide any stacktrace information)
          Command duration or timeout: 0 milliseconds

          Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'


          Your main issue is the version compatibility between the binaries you are using as follows :




          • You are using chromedriver=2.33

          • Release Notes of chromedriver=2.33 clearly mentions the following :



          Supports Chrome v60-62





          • You are using chrome=65.0

          • Release Notes of ChromeDriver v2.37 clearly mentions the following :



          Supports Chrome v64-66




          So there is a clear mismatch between the ChromeDriver version (v2.33) and the Chrome Browser version (v65.0)



          Solution




          • Upgrade ChromeDriver to current ChromeDriver v2.37 level.

          • Keep Chrome version at Chrome v65.x levels. (as per ChromeDriver v2.37 release notes)


          • Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.

          • Use CCleaner tool to wipe off all the OS chores before and after the execution of your test Suite.

          • If your base Web Client version is too old, then uninstall it through Revo Uninstaller and install a recent GA and released version of Web Client.

          • Execute your @Test.






          share|improve this answer





























            3














            The latest chrome browser requires corresponding latest chromedriver executable for the tests to run.






            share|improve this answer





























              2














              I have encountered the same issue and installed the chrome drive. Issue got resolved.



              npm install chromedriver --chromedriver_version=LATEST






              share|improve this answer































                2














                Changing latest version of ChromDriver worked for me.






                share|improve this answer





























                  1














                  You may need to update you driver the link for all the chromedriver updates are http://chromedriver.storage.googleapis.com/index.html
                  make sure you chromedriver corresponds to your version of chrome






                  share|improve this answer





























                    0














                    I simply installed a new version of Katalon Studio and it has worked fine.






                    share|improve this answer

















                    • 2




                      Sorry but this solution (if correct) highly depends on the workflow of the user who posted the question. Introducing a new tool when there's no real need looks like a desperate attempt to solve the issue without really understanding the nature/source of the problem.
                      – AirieFenix
                      Apr 9 at 18:57










                    protected by Community Mar 16 at 7:22



                    Thank you for your interest in this question.
                    Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                    Would you like to answer one of these unanswered questions instead?














                    7 Answers
                    7






                    active

                    oldest

                    votes








                    7 Answers
                    7






                    active

                    oldest

                    votes









                    active

                    oldest

                    votes






                    active

                    oldest

                    votes









                    105














                    I was seeing the same issue. The problem only appears when using Chrome 65 (currently: dev channel). With Chrome 64 (both stable channel and beta channel) everything worked fine.



                    It turns out I had an old chromedriver installed. Specifically, I was using chrome=65.0.3325.51 with chromedriver=2.29.461585. Running npm install -g chromedriver bumped chromedriver to 2.35.528157 and now the problem is solved. Hope this helps!



                    TL;DR: run npm install -g chromedriver






                    share|improve this answer



















                    • 2




                      Thanks! It worked. Updated the chrome driver to 2.35
                      – maharaja
                      Feb 8 at 17:37










                    • You're welcome. If the answer solves your problem, it's customary to mark it as "accepted answer".
                      – Martijn
                      Feb 8 at 21:39






                    • 2




                      chromedriver v2.35 supports chrome 62-64 at the moment
                      – Anton
                      Feb 26 at 16:13










                    • I updated this to 2.38.0, But when I check the version, it always says 2.33. I have changed the package.config (Visual Studio C#)...I cannot find any reference to 2.33 anymore. Where could this be? I tried to delete the project and recreate it.I am using the standalone selenium server..
                      – Greg P
                      Apr 23 at 12:25










                    • my chromedriver didn't automatically update in katalon studio. why is this and what can I do about it?
                      – user74843
                      May 25 at 14:41
















                    105














                    I was seeing the same issue. The problem only appears when using Chrome 65 (currently: dev channel). With Chrome 64 (both stable channel and beta channel) everything worked fine.



                    It turns out I had an old chromedriver installed. Specifically, I was using chrome=65.0.3325.51 with chromedriver=2.29.461585. Running npm install -g chromedriver bumped chromedriver to 2.35.528157 and now the problem is solved. Hope this helps!



                    TL;DR: run npm install -g chromedriver






                    share|improve this answer



















                    • 2




                      Thanks! It worked. Updated the chrome driver to 2.35
                      – maharaja
                      Feb 8 at 17:37










                    • You're welcome. If the answer solves your problem, it's customary to mark it as "accepted answer".
                      – Martijn
                      Feb 8 at 21:39






                    • 2




                      chromedriver v2.35 supports chrome 62-64 at the moment
                      – Anton
                      Feb 26 at 16:13










                    • I updated this to 2.38.0, But when I check the version, it always says 2.33. I have changed the package.config (Visual Studio C#)...I cannot find any reference to 2.33 anymore. Where could this be? I tried to delete the project and recreate it.I am using the standalone selenium server..
                      – Greg P
                      Apr 23 at 12:25










                    • my chromedriver didn't automatically update in katalon studio. why is this and what can I do about it?
                      – user74843
                      May 25 at 14:41














                    105












                    105








                    105






                    I was seeing the same issue. The problem only appears when using Chrome 65 (currently: dev channel). With Chrome 64 (both stable channel and beta channel) everything worked fine.



                    It turns out I had an old chromedriver installed. Specifically, I was using chrome=65.0.3325.51 with chromedriver=2.29.461585. Running npm install -g chromedriver bumped chromedriver to 2.35.528157 and now the problem is solved. Hope this helps!



                    TL;DR: run npm install -g chromedriver






                    share|improve this answer














                    I was seeing the same issue. The problem only appears when using Chrome 65 (currently: dev channel). With Chrome 64 (both stable channel and beta channel) everything worked fine.



                    It turns out I had an old chromedriver installed. Specifically, I was using chrome=65.0.3325.51 with chromedriver=2.29.461585. Running npm install -g chromedriver bumped chromedriver to 2.35.528157 and now the problem is solved. Hope this helps!



                    TL;DR: run npm install -g chromedriver







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Apr 17 at 9:02

























                    answered Feb 7 at 13:36









                    Martijn

                    3,63042134




                    3,63042134








                    • 2




                      Thanks! It worked. Updated the chrome driver to 2.35
                      – maharaja
                      Feb 8 at 17:37










                    • You're welcome. If the answer solves your problem, it's customary to mark it as "accepted answer".
                      – Martijn
                      Feb 8 at 21:39






                    • 2




                      chromedriver v2.35 supports chrome 62-64 at the moment
                      – Anton
                      Feb 26 at 16:13










                    • I updated this to 2.38.0, But when I check the version, it always says 2.33. I have changed the package.config (Visual Studio C#)...I cannot find any reference to 2.33 anymore. Where could this be? I tried to delete the project and recreate it.I am using the standalone selenium server..
                      – Greg P
                      Apr 23 at 12:25










                    • my chromedriver didn't automatically update in katalon studio. why is this and what can I do about it?
                      – user74843
                      May 25 at 14:41














                    • 2




                      Thanks! It worked. Updated the chrome driver to 2.35
                      – maharaja
                      Feb 8 at 17:37










                    • You're welcome. If the answer solves your problem, it's customary to mark it as "accepted answer".
                      – Martijn
                      Feb 8 at 21:39






                    • 2




                      chromedriver v2.35 supports chrome 62-64 at the moment
                      – Anton
                      Feb 26 at 16:13










                    • I updated this to 2.38.0, But when I check the version, it always says 2.33. I have changed the package.config (Visual Studio C#)...I cannot find any reference to 2.33 anymore. Where could this be? I tried to delete the project and recreate it.I am using the standalone selenium server..
                      – Greg P
                      Apr 23 at 12:25










                    • my chromedriver didn't automatically update in katalon studio. why is this and what can I do about it?
                      – user74843
                      May 25 at 14:41








                    2




                    2




                    Thanks! It worked. Updated the chrome driver to 2.35
                    – maharaja
                    Feb 8 at 17:37




                    Thanks! It worked. Updated the chrome driver to 2.35
                    – maharaja
                    Feb 8 at 17:37












                    You're welcome. If the answer solves your problem, it's customary to mark it as "accepted answer".
                    – Martijn
                    Feb 8 at 21:39




                    You're welcome. If the answer solves your problem, it's customary to mark it as "accepted answer".
                    – Martijn
                    Feb 8 at 21:39




                    2




                    2




                    chromedriver v2.35 supports chrome 62-64 at the moment
                    – Anton
                    Feb 26 at 16:13




                    chromedriver v2.35 supports chrome 62-64 at the moment
                    – Anton
                    Feb 26 at 16:13












                    I updated this to 2.38.0, But when I check the version, it always says 2.33. I have changed the package.config (Visual Studio C#)...I cannot find any reference to 2.33 anymore. Where could this be? I tried to delete the project and recreate it.I am using the standalone selenium server..
                    – Greg P
                    Apr 23 at 12:25




                    I updated this to 2.38.0, But when I check the version, it always says 2.33. I have changed the package.config (Visual Studio C#)...I cannot find any reference to 2.33 anymore. Where could this be? I tried to delete the project and recreate it.I am using the standalone selenium server..
                    – Greg P
                    Apr 23 at 12:25












                    my chromedriver didn't automatically update in katalon studio. why is this and what can I do about it?
                    – user74843
                    May 25 at 14:41




                    my chromedriver didn't automatically update in katalon studio. why is this and what can I do about it?
                    – user74843
                    May 25 at 14:41













                    15














                    The error says it all :



                    Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'

                    (Session info: chrome=65.0.3325.31)
                    (Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86)
                    (WARNING: The server did not provide any stacktrace information)
                    Command duration or timeout: 0 milliseconds

                    Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'


                    Your main issue is the version compatibility between the binaries you are using as follows :




                    • You are using chromedriver=2.33

                    • Release Notes of chromedriver=2.33 clearly mentions the following :



                    Supports Chrome v60-62





                    • You are using chrome=65.0

                    • Release Notes of ChromeDriver v2.37 clearly mentions the following :



                    Supports Chrome v64-66




                    So there is a clear mismatch between the ChromeDriver version (v2.33) and the Chrome Browser version (v65.0)



                    Solution




                    • Upgrade ChromeDriver to current ChromeDriver v2.37 level.

                    • Keep Chrome version at Chrome v65.x levels. (as per ChromeDriver v2.37 release notes)


                    • Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.

                    • Use CCleaner tool to wipe off all the OS chores before and after the execution of your test Suite.

                    • If your base Web Client version is too old, then uninstall it through Revo Uninstaller and install a recent GA and released version of Web Client.

                    • Execute your @Test.






                    share|improve this answer


























                      15














                      The error says it all :



                      Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'

                      (Session info: chrome=65.0.3325.31)
                      (Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86)
                      (WARNING: The server did not provide any stacktrace information)
                      Command duration or timeout: 0 milliseconds

                      Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'


                      Your main issue is the version compatibility between the binaries you are using as follows :




                      • You are using chromedriver=2.33

                      • Release Notes of chromedriver=2.33 clearly mentions the following :



                      Supports Chrome v60-62





                      • You are using chrome=65.0

                      • Release Notes of ChromeDriver v2.37 clearly mentions the following :



                      Supports Chrome v64-66




                      So there is a clear mismatch between the ChromeDriver version (v2.33) and the Chrome Browser version (v65.0)



                      Solution




                      • Upgrade ChromeDriver to current ChromeDriver v2.37 level.

                      • Keep Chrome version at Chrome v65.x levels. (as per ChromeDriver v2.37 release notes)


                      • Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.

                      • Use CCleaner tool to wipe off all the OS chores before and after the execution of your test Suite.

                      • If your base Web Client version is too old, then uninstall it through Revo Uninstaller and install a recent GA and released version of Web Client.

                      • Execute your @Test.






                      share|improve this answer
























                        15












                        15








                        15






                        The error says it all :



                        Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'

                        (Session info: chrome=65.0.3325.31)
                        (Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86)
                        (WARNING: The server did not provide any stacktrace information)
                        Command duration or timeout: 0 milliseconds

                        Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'


                        Your main issue is the version compatibility between the binaries you are using as follows :




                        • You are using chromedriver=2.33

                        • Release Notes of chromedriver=2.33 clearly mentions the following :



                        Supports Chrome v60-62





                        • You are using chrome=65.0

                        • Release Notes of ChromeDriver v2.37 clearly mentions the following :



                        Supports Chrome v64-66




                        So there is a clear mismatch between the ChromeDriver version (v2.33) and the Chrome Browser version (v65.0)



                        Solution




                        • Upgrade ChromeDriver to current ChromeDriver v2.37 level.

                        • Keep Chrome version at Chrome v65.x levels. (as per ChromeDriver v2.37 release notes)


                        • Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.

                        • Use CCleaner tool to wipe off all the OS chores before and after the execution of your test Suite.

                        • If your base Web Client version is too old, then uninstall it through Revo Uninstaller and install a recent GA and released version of Web Client.

                        • Execute your @Test.






                        share|improve this answer












                        The error says it all :



                        Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'

                        (Session info: chrome=65.0.3325.31)
                        (Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86)
                        (WARNING: The server did not provide any stacktrace information)
                        Command duration or timeout: 0 milliseconds

                        Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'


                        Your main issue is the version compatibility between the binaries you are using as follows :




                        • You are using chromedriver=2.33

                        • Release Notes of chromedriver=2.33 clearly mentions the following :



                        Supports Chrome v60-62





                        • You are using chrome=65.0

                        • Release Notes of ChromeDriver v2.37 clearly mentions the following :



                        Supports Chrome v64-66




                        So there is a clear mismatch between the ChromeDriver version (v2.33) and the Chrome Browser version (v65.0)



                        Solution




                        • Upgrade ChromeDriver to current ChromeDriver v2.37 level.

                        • Keep Chrome version at Chrome v65.x levels. (as per ChromeDriver v2.37 release notes)


                        • Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.

                        • Use CCleaner tool to wipe off all the OS chores before and after the execution of your test Suite.

                        • If your base Web Client version is too old, then uninstall it through Revo Uninstaller and install a recent GA and released version of Web Client.

                        • Execute your @Test.







                        share|improve this answer












                        share|improve this answer



                        share|improve this answer










                        answered Mar 27 at 9:56









                        DebanjanB

                        37.9k73375




                        37.9k73375























                            3














                            The latest chrome browser requires corresponding latest chromedriver executable for the tests to run.






                            share|improve this answer


























                              3














                              The latest chrome browser requires corresponding latest chromedriver executable for the tests to run.






                              share|improve this answer
























                                3












                                3








                                3






                                The latest chrome browser requires corresponding latest chromedriver executable for the tests to run.






                                share|improve this answer












                                The latest chrome browser requires corresponding latest chromedriver executable for the tests to run.







                                share|improve this answer












                                share|improve this answer



                                share|improve this answer










                                answered Mar 13 at 11:36









                                user1660026

                                312




                                312























                                    2














                                    I have encountered the same issue and installed the chrome drive. Issue got resolved.



                                    npm install chromedriver --chromedriver_version=LATEST






                                    share|improve this answer




























                                      2














                                      I have encountered the same issue and installed the chrome drive. Issue got resolved.



                                      npm install chromedriver --chromedriver_version=LATEST






                                      share|improve this answer


























                                        2












                                        2








                                        2






                                        I have encountered the same issue and installed the chrome drive. Issue got resolved.



                                        npm install chromedriver --chromedriver_version=LATEST






                                        share|improve this answer














                                        I have encountered the same issue and installed the chrome drive. Issue got resolved.



                                        npm install chromedriver --chromedriver_version=LATEST







                                        share|improve this answer














                                        share|improve this answer



                                        share|improve this answer








                                        edited Mar 17 at 19:49









                                        Gf Spa

                                        31




                                        31










                                        answered Mar 13 at 9:01









                                        Kumar Abhishek

                                        1,2781120




                                        1,2781120























                                            2














                                            Changing latest version of ChromDriver worked for me.






                                            share|improve this answer


























                                              2














                                              Changing latest version of ChromDriver worked for me.






                                              share|improve this answer
























                                                2












                                                2








                                                2






                                                Changing latest version of ChromDriver worked for me.






                                                share|improve this answer












                                                Changing latest version of ChromDriver worked for me.







                                                share|improve this answer












                                                share|improve this answer



                                                share|improve this answer










                                                answered Mar 19 at 4:53









                                                RohitKumar

                                                335




                                                335























                                                    1














                                                    You may need to update you driver the link for all the chromedriver updates are http://chromedriver.storage.googleapis.com/index.html
                                                    make sure you chromedriver corresponds to your version of chrome






                                                    share|improve this answer


























                                                      1














                                                      You may need to update you driver the link for all the chromedriver updates are http://chromedriver.storage.googleapis.com/index.html
                                                      make sure you chromedriver corresponds to your version of chrome






                                                      share|improve this answer
























                                                        1












                                                        1








                                                        1






                                                        You may need to update you driver the link for all the chromedriver updates are http://chromedriver.storage.googleapis.com/index.html
                                                        make sure you chromedriver corresponds to your version of chrome






                                                        share|improve this answer












                                                        You may need to update you driver the link for all the chromedriver updates are http://chromedriver.storage.googleapis.com/index.html
                                                        make sure you chromedriver corresponds to your version of chrome







                                                        share|improve this answer












                                                        share|improve this answer



                                                        share|improve this answer










                                                        answered Mar 16 at 18:58









                                                        Matt

                                                        9671316




                                                        9671316























                                                            0














                                                            I simply installed a new version of Katalon Studio and it has worked fine.






                                                            share|improve this answer

















                                                            • 2




                                                              Sorry but this solution (if correct) highly depends on the workflow of the user who posted the question. Introducing a new tool when there's no real need looks like a desperate attempt to solve the issue without really understanding the nature/source of the problem.
                                                              – AirieFenix
                                                              Apr 9 at 18:57
















                                                            0














                                                            I simply installed a new version of Katalon Studio and it has worked fine.






                                                            share|improve this answer

















                                                            • 2




                                                              Sorry but this solution (if correct) highly depends on the workflow of the user who posted the question. Introducing a new tool when there's no real need looks like a desperate attempt to solve the issue without really understanding the nature/source of the problem.
                                                              – AirieFenix
                                                              Apr 9 at 18:57














                                                            0












                                                            0








                                                            0






                                                            I simply installed a new version of Katalon Studio and it has worked fine.






                                                            share|improve this answer












                                                            I simply installed a new version of Katalon Studio and it has worked fine.







                                                            share|improve this answer












                                                            share|improve this answer



                                                            share|improve this answer










                                                            answered Mar 28 at 13:58









                                                            nix86

                                                            95041539




                                                            95041539








                                                            • 2




                                                              Sorry but this solution (if correct) highly depends on the workflow of the user who posted the question. Introducing a new tool when there's no real need looks like a desperate attempt to solve the issue without really understanding the nature/source of the problem.
                                                              – AirieFenix
                                                              Apr 9 at 18:57














                                                            • 2




                                                              Sorry but this solution (if correct) highly depends on the workflow of the user who posted the question. Introducing a new tool when there's no real need looks like a desperate attempt to solve the issue without really understanding the nature/source of the problem.
                                                              – AirieFenix
                                                              Apr 9 at 18:57








                                                            2




                                                            2




                                                            Sorry but this solution (if correct) highly depends on the workflow of the user who posted the question. Introducing a new tool when there's no real need looks like a desperate attempt to solve the issue without really understanding the nature/source of the problem.
                                                            – AirieFenix
                                                            Apr 9 at 18:57




                                                            Sorry but this solution (if correct) highly depends on the workflow of the user who posted the question. Introducing a new tool when there's no real need looks like a desperate attempt to solve the issue without really understanding the nature/source of the problem.
                                                            – AirieFenix
                                                            Apr 9 at 18:57





                                                            protected by Community Mar 16 at 7:22



                                                            Thank you for your interest in this question.
                                                            Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                                            Would you like to answer one of these unanswered questions instead?



                                                            Popular posts from this blog

                                                            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

                                                            Calculate evaluation metrics using cross_val_predict sklearn

                                                            Insert data from modal to MySQL (multiple modal on website)