Absolute vs relative XPath in Selenium Java - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to find an element using an absolute XPath.

Selenium Java

WebElement element = driver.findElement(By.xpath("[1]"));

Drag options to blanks, or click blank then click option'

A"/html/body/div[1]/div[2]/button"

B"//button[@id='submit']"

C".//div[@class='container']"

D"//*[@class='btn']"

Attempts:

3 left

💡 Hint

Common Mistakes

Using relative XPath when absolute is required.

Starting XPath with '//' for absolute path.

An absolute XPath starts from the root node and follows the full path.

2fill in blank

medium

Complete the code to find an element using a relative XPath.

Selenium Java

WebElement element = driver.findElement(By.xpath("[1]"));

Drag options to blanks, or click blank then click option'

A"//button[@id='submit']"

B"/html/body//button"

C"/html/body/div[1]/div[2]/button"

D"/html//div/button"

Attempts:

3 left

💡 Hint

Common Mistakes

Using absolute XPath when relative is better.

Missing the double slashes at the start.

A relative XPath starts with '//' and finds elements anywhere in the document.

3fill in blank

hard

Fix the error in the XPath to correctly select the button with id 'login'.

Selenium Java

WebElement loginButton = driver.findElement(By.xpath("[1]"));

Drag options to blanks, or click blank then click option'

A"//button[id='login']"

B"/button[@id='login']"

C"button[@id='login']"

D"//button[@id='login']"

Attempts:

3 left

💡 Hint

Common Mistakes

Using single slash '/' which looks only at direct children.

Missing '@' before attribute name.

Using 'id' without '@'.

The correct XPath uses '//' to search anywhere and '@' to specify attribute.

4fill in blank

hard

Fill both blanks to create a relative XPath that selects all div elements with class 'content'.

Selenium Java

List<WebElement> divs = driver.findElements(By.xpath("[1][@class=[2]]"));

Drag options to blanks, or click blank then click option'

A"//div"

B"content"

C"'content'"

D"div"

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the attribute value.

Using single slash '/' instead of '//'.

The XPath selects all div elements (//div) with class attribute equal to 'content' ([@class='content']).

5fill in blank

hard

Fill all three blanks to create an XPath that selects input elements with type 'text' inside a form with id 'searchForm'.

Selenium Java

WebElement input = driver.findElement(By.xpath("[1][@id=[2]]//[3][@type='text']"));

Drag options to blanks, or click blank then click option'

A"//form"

B"'searchForm'"

C"input"

D"form"

Attempts:

3 left

💡 Hint

Common Mistakes

Using single slash '/' instead of '//' for relative paths.

Not quoting attribute values.

Using wrong element names.

The XPath selects a form element with id 'searchForm' and then finds input elements with type 'text' inside it.

Practice

1. Which of the following best describes an absolute XPath?

easy

A. It uses CSS selectors to locate elements.

B. It starts anywhere in the document using // to find elements by attribute.

C. It starts from the root node and follows the full path to the element.

D. It only works with elements having unique IDs.

Solution

1. Step 1: Understand XPath types

   Absolute XPath always starts from the root node, indicated by a single slash (/), and follows the full path down to the target element.

2. Step 2: Compare with relative XPath

   Relative XPath starts with double slashes (//) and can start anywhere in the document, not necessarily from the root.

3. Final Answer:

   It starts from the root node and follows the full path to the element. -> Option C

4. Quick Check:

   Absolute XPath = full path from root [OK]

Hint: Absolute XPath starts with / from root, relative with // anywhere [OK]

Common Mistakes:

• Confusing absolute with relative XPath syntax
• Thinking relative XPath always starts from root
• Assuming absolute XPath uses //
• Believing XPath only works with unique IDs

2. Which of the following is a correct relative XPath syntax to find a button with text 'Submit'?

easy

A. //button[text()='Submit']

B. /html/body/button[text()='Submit']

C. button[text()='Submit']

D. //*[@id='Submit']

Solution

1. Step 1: Identify relative XPath syntax

   Relative XPath uses // to search anywhere in the document. The expression //button[text()='Submit'] finds any button element with exact text 'Submit'.

2. Step 2: Check other options

   /html/body/button[text()='Submit'] is absolute XPath, not relative. button[text()='Submit'] is invalid because it lacks // or /. //*[@id='Submit'] looks for an element with id='Submit', not text.

3. Final Answer:

   //button[text()='Submit'] -> Option A

4. Quick Check:

   Relative XPath uses // and matches element by text [OK]

Hint: Relative XPath starts with // and matches anywhere [OK]

Common Mistakes:

• Using single slash / for relative XPath
• Omitting // before element name
• Confusing attribute and text matching
• Using absolute path syntax for relative XPath

3. Given the HTML snippet:

<div>
  <ul>
    <li>Home</li>
    <li>About</li>
    <li>Contact</li>
  </ul>
</div>

What element does the XPath //ul/li[2] select?

medium

A. The second <li> element inside <ul>

B. The first <li> element inside <ul>

C. The <ul> element itself

D. No element, XPath is invalid

Solution

1. Step 1: Understand XPath expression

   //ul finds any <ul> element anywhere. li[2] selects the second <li> child of that <ul>.

2. Step 2: Identify the second <li> in the HTML

   The <li> elements are: 1) Home, 2) About, 3) Contact. So li[2] is <li>About</li>.

3. Final Answer:

   The second <li> element inside <ul> -> Option A

4. Quick Check:

   //ul/li[2] = second list item [OK]

Hint: li[n] selects nth child li under the matched parent [OK]

Common Mistakes:

• Confusing li[2] with the first li
• Thinking XPath selects ul element
• Assuming XPath is invalid syntax
• Mixing absolute and relative XPath concepts

4. You wrote this XPath to find a login button:
/html/body/div/button[@id='loginBtn']
But your test fails when the page structure changes slightly. What is the best fix?

medium

A. Add more parent nodes to the XPath

B. Keep the same XPath; the failure is unrelated

C. Use CSS selector instead of XPath

D. Change to relative XPath: //button[@id='loginBtn']

Solution

1. Step 1: Analyze the problem with absolute XPath

   Absolute XPath starts from root and depends on full path. If page structure changes, the path breaks and test fails.

2. Step 2: Use relative XPath for stability

   Relative XPath like //button[@id='loginBtn'] finds the button anywhere by id, making tests more stable and maintainable.

3. Final Answer:

   Change to relative XPath: //button[@id='loginBtn'] -> Option D

4. Quick Check:

   Relative XPath is more stable than absolute [OK]

Hint: Use // and attributes for stable locators, not full paths [OK]

Common Mistakes:

• Adding more parents makes XPath fragile
• Ignoring XPath type causes flaky tests
• Assuming CSS selector always better
• Not updating XPath after page changes

5. You want to locate an input field inside a form, but the form's position in the page changes often. Which XPath is best to locate the input with name='email' reliably?

hard

A. /html/body/div[2]/form/input[@name='email']

B. //form//input[@name='email']

C. /form/input[@name='email']

D. //input[@id='emailField']

Solution

1. Step 1: Evaluate absolute XPath option

   /html/body/div[2]/form/input[@name='email'] is absolute and depends on exact page structure, which changes often, so it's fragile.

2. Step 2: Evaluate relative XPath options

   //form//input[@name='email'] finds input with name='email' anywhere inside any form, making it flexible and stable despite page changes. /form/input[@name='email'] is invalid because it starts from root but form is not root. //input[@id='emailField'] depends on id which may not exist or be different.

3. Final Answer:

   //form//input[@name='email'] -> Option B

4. Quick Check:

   Relative XPath with attributes inside form is best [OK]

Hint: Use //form//input[@name='email'] for flexible, stable locating [OK]

Common Mistakes:

• Using absolute XPath that breaks on layout changes
• Assuming input has id when it may not
• Starting XPath from root incorrectly
• Not using // to search anywhere inside form