Choosing XPath vs CSS strategy in Selenium Java - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

When to prefer XPath over CSS selectors?

In Selenium Java tests, which situation best justifies choosing XPath over CSS selectors?

A When you want to select elements using simple tag names.

B When you want to select elements by ID attribute.

C When you need to select elements based on their text content.

D When you want to select elements by class name only.

💡 Hint

Think about which selector can handle text content filtering.

XPath supports selecting elements by their text content, which CSS selectors cannot do. CSS selectors are better for simple attribute or class selections.

❓ Predict Output

intermediate

Output of locating elements with XPath vs CSS

Given the HTML snippet below, what is the number of elements matched by each locator?

<ul>
  <li class="item">Apple</li>
  <li class="item">Banana</li>
  <li class="item">Cherry</li>
</ul>

Which option correctly states the number of elements found by these locators?

XPath: //li[contains(text(),'a')]
CSS: li.item

A XPath finds 2 elements; CSS finds 3 elements.

B XPath finds 3 elements; CSS finds 2 elements.

C XPath finds 1 element; CSS finds 3 elements.

D XPath finds 3 elements; CSS finds 3 elements.

💡 Hint

Check which list items contain the letter 'a' in their text.

The XPath locator selects <li> elements whose text contains 'a'. 'Banana' and 'Cherry' contain 'a', so 2 elements. The CSS selector selects all <li> elements with class 'item', which are all 3.

❓ assertion

advanced

Correct assertion for element text using XPath

Which assertion correctly verifies that the element located by XPath //button[@id='submit'] has the exact text 'Submit' in Selenium Java?

Selenium Java

WebElement button = driver.findElement(By.xpath("//button[@id='submit']"));

A assertNull(button.getText());

B assertTrue(button.getText().contains("Submit"));

C assertFalse(button.getText().equals("Submit"));

D assertEquals("Submit", button.getText());

💡 Hint

Exact text match requires equality assertion.

assertEquals checks that the button's text exactly matches 'Submit'. Using contains or assertFalse would not verify exact match. assertNull is incorrect because the text is expected.

🔧 Debug

advanced

Why does this CSS selector fail to locate the element?

Given the HTML below, why does the CSS selector div#main > span.highlighted fail to find the <span> element?

<div id="main">
  <div>
    <span class="highlighted">Text</span>
  </div>
</div>

A Because the &lt;span&gt; is not a direct child of &lt;div id="main"&gt; but a grandchild.

B Because the &lt;span&gt; does not have the class 'highlighted'.

C Because the CSS selector syntax is invalid.

D Because the &lt;div&gt; with id 'main' does not exist.

💡 Hint

Check the relationship between elements in the selector.

The '>' combinator in CSS means direct child. The <span> is inside a nested <div>, so it is a grandchild, not a direct child, causing the selector to fail.

❓ framework

expert

Choosing locator strategy for dynamic elements in Selenium Java

You have a web page where element IDs change every time the page loads, but the element has a stable class and contains specific text. Which locator strategy is best to reliably find this element?

A Use CSS selector with ID attribute.

B Use XPath with contains() to match the stable class and text content.

C Use XPath with exact ID match.

D Use CSS selector with tag name only.

💡 Hint

Think about how to handle dynamic IDs and stable attributes.

XPath allows combining conditions like contains() on class and text(), which helps locate elements with dynamic IDs but stable other attributes. CSS selectors cannot filter by text content.