Absolute vs relative XPath in Selenium Python - Test Execution Compared

Test Overview

This test opens a webpage and locates a button using both absolute and relative XPath. It verifies that the button is clickable and has the expected text.

Test Code - Selenium

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
import unittest

class TestXPath(unittest.TestCase):
    def setUp(self):
        self.driver = webdriver.Chrome()
        self.driver.get('https://example.com/testpage')

    def test_button_xpath(self):
        driver = self.driver
        wait = WebDriverWait(driver, 10)

        # Locate button using absolute XPath
        abs_xpath = '/html/body/div/main/section/button'
        button_abs = wait.until(EC.element_to_be_clickable((By.XPATH, abs_xpath)))
        self.assertEqual(button_abs.text, 'Click Me')

        # Locate button using relative XPath
        rel_xpath = '//section/button'
        button_rel = wait.until(EC.element_to_be_clickable((By.XPATH, rel_xpath)))
        self.assertEqual(button_rel.text, 'Click Me')

    def tearDown(self):
        self.driver.quit()

if __name__ == '__main__':
    unittest.main()

Execution Trace - 5 Steps

Step	Action	System State	Assertion	Result
1	Test starts and Chrome browser opens	Browser window is open, ready to load the test page	—	PASS
2	Browser navigates to 'https://example.com/testpage'	Page loads with a main section containing a button labeled 'Click Me'	—	PASS
3	Wait until the button is clickable using absolute XPath '/html/body/div/main/section/button'	Button element is found and clickable	Check that button text equals 'Click Me'	PASS
4	Wait until the button is clickable using relative XPath '//section/button'	Button element is found and clickable	Check that button text equals 'Click Me'	PASS
5	Test ends and browser closes	Browser window closes	—	PASS

Failure Scenario

Failing Condition: The XPath does not locate the button because the page structure changed or XPath is incorrect

Execution Trace Quiz - 3 Questions

Which XPath is more fragile to page structure changes?

A Both are equally fragile

B Absolute XPath

C Relative XPath

D Neither is fragile

Key Result

Using relative XPath is a best practice because it is less likely to break when the page layout changes, making tests more stable.

Practice

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

easy

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

B. It starts from any node and uses conditions to find the element.

C. It uses CSS selectors instead of XML paths.

D. It only works with HTML tables.

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 to the target element.

2. Step 2: Compare with relative XPath

   Relative XPath starts from anywhere in the document, often using double slashes (//) and conditions to locate elements.

3. Final Answer:

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

4. Quick Check:

   Absolute XPath = full path from root [OK]

Hint: Absolute XPath always starts with a single slash / [OK]

Common Mistakes:

• Confusing absolute with relative XPath syntax
• Thinking relative XPath always starts at root
• Assuming absolute XPath uses conditions only

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

easy

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

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

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

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

Solution

1. Step 1: Identify relative XPath syntax

   Relative XPath uses double slashes (//) to search anywhere in the document for matching elements.

2. Step 2: Check the options

   //button[text()='Submit'] uses //button[text()='Submit'], which correctly finds a button element with exact text 'Submit'. /html/body/button[text()='Submit'] is absolute XPath. button[text()='Submit'] misses the // and is invalid XPath. //*[@id='submit'] uses an attribute selector but does not specify text.

3. Final Answer:

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

4. Quick Check:

   Relative XPath uses // and conditions [OK]

Hint: Relative XPath starts with // and uses conditions [OK]

Common Mistakes:

• Using single slash / for relative XPath
• Omitting // before element name
• Confusing attribute and text selectors

3. Given the following HTML snippet:

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

What will the XPath //ul/li[2] select?

medium

A. The second list item <li>About</li>

B. The third list item <li>Contact</li>

C. The first list item <li>Home</li>

D. No element, XPath is invalid

Solution

1. Step 1: Understand the XPath expression

   The XPath //ul/li[2] selects the second
2. child element of any <ul> element anywhere in the document.

3. Step 2: Match with HTML structure

   The <ul> has three
4. children: Home (1), About (2), Contact (3). So li[2] selects About.

5. Final Answer:

   The second list item <li>About</li> -> Option A

6. Quick Check:

   li[2] = second child element [OK]

Hint: XPath [n] selects the nth child element [OK]

Common Mistakes:

• Confusing index starting at 0 instead of 1
• Thinking //ul/li[2] selects second ul element
• Assuming XPath is zero-based

4. You wrote this XPath to find a login button:
/html/body/div/button[@id='login']
But your test fails to find the element after page update. What is the likely issue?

medium

A. XPath cannot find buttons.

B. The XPath uses wrong attribute syntax.

C. The button does not have an id attribute.

D. The XPath is absolute and fragile; page structure changed breaking the path.

Solution

1. Step 1: Analyze the XPath type

   The XPath starts with a single slash /, so it is absolute and depends on the full path from root.

2. Step 2: Understand fragility of absolute XPath

   If the page structure changes (like adding a div), the absolute path breaks and element is not found.

3. Final Answer:

   The XPath is absolute and fragile; page structure changed breaking the path. -> Option D

4. Quick Check:

   Absolute XPath breaks if page structure changes [OK]

Hint: Avoid absolute XPath for dynamic pages [OK]

Common Mistakes:

• Blaming attribute syntax instead of XPath type
• Assuming XPath cannot find buttons
• Ignoring page structure changes

5. You want to write a stable XPath to find a product name inside a list where the product has a price of '$20'. The HTML structure is:

<div class='product'>
  <span class='name'>Product A</span>
  <span class='price'>$20</span>
</div>
<div class='product'>
  <span class='name'>Product B</span>
  <span class='price'>$30</span>
</div>

Which XPath is best to find the name of the product priced $20?

hard

A. //span[@class='price' and text()='$20']/preceding-sibling::span[@class='name']

B. /html/body/div[1]/span[1]

C. //div[@class='product'][span[@class='price' and text()='$20']]//span[@class='name']

D. //div[@class='product']/span[@class='name']

Solution

1. Step 1: Understand the requirement

   We want the product name where the price is exactly '$20'. So we must find a product div with a price span of '$20' and then get its name span.

2. Step 2: Evaluate each XPath

   //div[@class='product'][span[@class='price' and text()='$20']]//span[@class='name'] selects div with class 'product' having a span price '$20', then selects the name span inside it. This is precise and stable.
   /html/body/div[1]/span[1] is absolute XPath and fragile.
   //span[@class='price' and text()='$20']/preceding-sibling::span[@class='name'] tries to find price span then preceding sibling name span, which matches the HTML structure where name is before price.
   //div[@class='product']/span[@class='name'] selects all product names, ignoring price.

3. Final Answer:

   //div[@class='product'][span[@class='price' and text()='$20']]//span[@class='name'] -> Option C

4. Quick Check:

   Use relative XPath with conditions for stable element [OK]

Hint: Use relative XPath with conditions to target elements precisely [OK]

Common Mistakes:

• Using absolute XPath that breaks easily
• Selecting elements without conditions
• Ignoring element hierarchy in XPath