Selenium Web Element Locators & Selectors 3

Question 1

What is the recommended approach for locating elements whose IDs are dynamically generated and change on every page load?

Accepted Answer

Use By.cssSelector() with a stable data-testid attribute

Answer

Stable attributes like data-testid are explicitly added for testing and are unaffected by dynamic ID generation.

Question 2

Which CSS selector matches <input> elements whose placeholder attribute CONTAINS the string 'email'?

Accepted Answer

input[placeholder*='email']

Answer

The *= operator in CSS attribute selectors matches elements whose attribute value contains the specified substring.

Question 3

Which of the following correctly selects the third

element within a

using XPath?

Accepted Answer

Both //ul/li[position()=3] and //ul/li[3]

Answer

Both //ul/li[3] (positional predicate shorthand) and //ul/li[position()=3] are equivalent expressions selecting the third <li> child.

Question 4

Why is absolute XPath generally considered fragile and discouraged in Selenium test suites?

Accepted Answer

It breaks whenever any ancestor element in the fixed path is changed or reordered

Answer

Absolute XPath traces a fixed path from the HTML root, so any structural change to the page hierarchy invalidates the locator.

Question 5

Which Selenium locator strategy generally provides better execution performance than XPath in most browsers?

Accepted Answer

By.cssSelector()

Answer

CSS selectors are natively implemented in browser rendering engines and typically execute faster than XPath, which requires a separate engine.

(Selenium) Selenium Testing Certification Practice Test