selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element while trying to click Next button with selenium

Question

So Im trying to I click the next button using selenium, I\'ve tried with the code below, but it ends in error.

The element

Answer 1

This error message...

selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"name","selector":"submitNext"}
  (Session info: chrome=66.0.3359.170)
  (Driver info: chromedriver=2.36.540470)

...implies that the ChromeDriver was unable to locate the desired element.

Locating the desired element

As per the HTML you have shared to click on the element you can use either of the following Locator Strategies :

• css_selector :

  driver.find_element_by_css_selector("input[name='submitNext'][value='Next']").click()
  

• xpath :

  driver.find_element_by_xpath("//input[@name='submitNext' and @value='Next']").click()
  

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

• You are using chromedriver=2.36
• Release Notes of chromedriver=2.36 clearly mentions the following :

Supports Chrome v63-65

• You are using chrome=66.0
• Release Notes of ChromeDriver v2.38 clearly mentions the following :

Supports Chrome v65-67

• Your Selenium Client version is unknown to us.

So there is a clear mismatch between the ChromeDriver v2.36 and the Chrome Browser v66.0

Solution

• Upgrade Selenium to current levels Version 3.11.0.
• Upgrade ChromeDriver to current ChromeDriver v2.38 level.
• Keep Chrome version at Chrome v66.x levels. (as per ChromeDriver v2.38 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.
• Take a System Reboot.
• Execute your @Test.