findElement by name in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of findElement by name with multiple matching elements

What will be the output of the following Selenium Java code snippet when multiple elements share the same name attribute?

Selenium Java

WebDriver driver = new ChromeDriver();
driver.get("https://example.com/form");
WebElement element = driver.findElement(By.name("username"));
System.out.println(element.getTagName());

A Throws StaleElementReferenceException immediately

B Throws NoSuchElementException because multiple elements have the same name

C Prints the tag name of all elements with name 'username'

D Prints the tag name of the first element with name 'username', e.g., 'input'

💡 Hint

findElement returns the first matching element, not all elements.

The findElement method returns the first WebElement matching the locator. Even if multiple elements share the same name, only the first is returned. No exception is thrown unless no elements match.

❓ assertion

intermediate

Correct assertion for element found by name

Which assertion correctly verifies that the element found by name 'email' is displayed on the page?

Selenium Java

WebElement emailField = driver.findElement(By.name("email"));

A assertNull(emailField);

B assertEquals(emailField.getText(), "email");

C assertTrue(emailField.isDisplayed());

D assertFalse(emailField.isEnabled());

💡 Hint

To check visibility, use isDisplayed() method.

The isDisplayed() method returns true if the element is visible on the page. The assertion assertTrue(emailField.isDisplayed()) correctly verifies this.

🔧 Debug

advanced

Debugging NoSuchElementException with findElement by name

Given the code below, why does it throw NoSuchElementException?

Selenium Java

driver.get("https://example.com/login");
WebElement password = driver.findElement(By.name("pass"));

A The driver is not initialized properly

B The page does not have any element with name attribute 'pass'

C The findElement method requires an ID locator, not name

D The element is inside an iframe and not switched to it

💡 Hint

Check the actual HTML for the name attribute value.

NoSuchElementException occurs when no element matches the locator. If the page has no element with name 'pass', this exception is thrown.

🧠 Conceptual

advanced

Behavior of findElement vs findElements by name

Which statement correctly describes the difference between findElement(By.name("user")) and findElements(By.name("user"))?

A findElement returns the first matching element or throws exception; findElements returns a list of all matching elements or empty list

B findElement returns a list of elements; findElements returns only the first element

C Both methods return the same result but findElements is slower

D findElement returns null if no element found; findElements throws exception

💡 Hint

One returns a single element, the other returns a list.

findElement returns the first matching element or throws NoSuchElementException if none found. findElements returns a list of all matching elements or an empty list if none found.

❓ framework

expert

Best practice for waiting for element by name before interaction

In Selenium Java, which code snippet correctly waits up to 10 seconds for an element with name 'submit' to be clickable before clicking it?

A new WebDriverWait(driver, Duration.ofSeconds(10)).until(ExpectedConditions.elementToBeClickable(By.name("submit"))).click();

B Thread.sleep(10000); driver.findElement(By.name("submit")).click();

C driver.findElement(By.name("submit")).click();

D driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS); driver.findElement(By.name("submit")).click();

💡 Hint

Explicit waits are better than implicit waits or sleep for waiting specific conditions.

Using WebDriverWait with ExpectedConditions.elementToBeClickable waits up to the timeout for the element to be clickable, then clicks it. This is the best practice for reliable interaction.