findElement by xpath in Selenium Java - Framework Patterns

Framework Mode - findElement by xpath

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   └── LoginPage.java
                ├── tests/
                │   └── LoginTest.java
                ├── utils/
                │   └── WebDriverFactory.java
                └── config/
                    └── ConfigReader.java

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown (e.g., WebDriverFactory.java).
• Page Objects: Classes representing pages, locating elements using findElement(By.xpath()) for UI interaction (e.g., LoginPage.java).
• Tests: Test classes that use page objects to perform actions and assertions (e.g., LoginTest.java).
• Utilities: Helper classes for common functions like waits, logging, or data handling.
• Configuration: Reads environment settings, browser types, and credentials (e.g., ConfigReader.java).

Configuration Patterns

• Use properties files to store environment URLs, browser types, and credentials.
• Load configurations at runtime using a ConfigReader utility class.
• Allow switching browsers (Chrome, Firefox) via config to run tests on different drivers.
• Keep sensitive data like passwords outside source code, use environment variables or encrypted files.

Test Reporting and CI/CD Integration

• Use TestNG built-in reports or integrate with Allure for detailed HTML reports.
• Configure test suites in TestNG XML files to organize and run tests.
• Integrate with CI/CD tools like Jenkins or GitHub Actions to run tests automatically on code changes.
• Publish reports as build artifacts and send notifications on test failures.

Framework Design Principles

1. Use Page Object Model: Encapsulate element locators and actions in page classes to keep tests clean.
2. Prefer explicit waits: Use WebDriverWait with conditions instead of implicit waits for reliable element finding.
3. Use descriptive XPath: Write clear and maintainable XPath expressions avoiding brittle absolute paths.
4. Separate config from code: Keep environment and browser settings outside test code for flexibility.
5. Keep tests independent: Each test should setup and cleanup its own state to avoid flaky results.

Self Check

Where in this folder structure would you add a new page object class for a "Dashboard" page that requires locating elements using XPath?

Key Result

Organize Selenium Java tests using Page Object Model with clear XPath locators, config management, and reporting.

Practice

1. What does the Selenium method findElement(By.xpath("//button[@id='submit']")) do?

easy

A. Finds the first button element with id 'submit' on the page

B. Finds all button elements with id 'submit' on the page

C. Clicks the button with id 'submit' automatically

D. Deletes the button element with id 'submit'

Solution

1. Step 1: Understand the method purpose

   The method findElement locates a single web element matching the given locator.

2. Step 2: Analyze the XPath expression

   The XPath //button[@id='submit'] selects the first <button> element with attribute id='submit'.

3. Final Answer:

   Finds the first button element with id 'submit' on the page -> Option A

4. Quick Check:

   findElement + XPath = single matching element [OK]

Hint: findElement returns one element matching XPath [OK]

Common Mistakes:

• Confusing findElement with findElements
• Thinking it clicks or deletes element
• Assuming it returns multiple elements

2. Which of the following is the correct syntax to find an element with XPath in Selenium Java?

easy

A. driver.findElement(By.xpath('//input[@name='username']'));

B. driver.findElement(By.xpath=//input[@name='username']);

C. driver.findElement(By.xpath("//input[@name='username']"));

D. driver.findElement(By.xpath("input[@name='username']"));

Solution

1. Step 1: Check method call syntax

   The correct method call is driver.findElement(By.xpath("xpath_string")) with double quotes around the XPath string.

2. Step 2: Validate each option

   driver.findElement(By.xpath("//input[@name='username']")); uses correct syntax with double quotes and proper method call. driver.findElement(By.xpath=//input[@name='username']); uses invalid assignment syntax. driver.findElement(By.xpath('//input[@name='username']')); uses single quotes inside double quotes incorrectly. driver.findElement(By.xpath("input[@name='username']")); misses the leading '//' in XPath.

3. Final Answer:

   driver.findElement(By.xpath("//input[@name='username']")); -> Option C

4. Quick Check:

   Correct method call with By.xpath and string [OK]

Hint: Use By.xpath("xpath") with double quotes inside parentheses [OK]

Common Mistakes:

• Using assignment '=' instead of method argument
• Mixing single and double quotes incorrectly
• Omitting '//' in XPath expression

3. What will be the result of this code snippet?

WebElement element = driver.findElement(By.xpath("//div[@class='menu']/ul/li[2]"));
System.out.println(element.getText());

Assuming the HTML is:

<div class='menu'>
  <ul>
    <li>Home</li>
    <li>About</li>
    <li>Contact</li>
  </ul>
</div>

medium

A. Home

B. NoSuchElementException

C. Contact

D. About

Solution

1. Step 1: Understand the XPath expression

   The XPath //div[@class='menu']/ul/li[2] selects the second <li> child inside the <ul> within the div with class 'menu'.

2. Step 2: Match XPath to HTML content

   The second <li> inside the list is About. So element.getText() will print "About".

3. Final Answer:

   About -> Option D

4. Quick Check:

   XPath li[2] = second list item text [OK]

Hint: XPath li[2] selects second list item text [OK]

Common Mistakes:

• Confusing index starting at 0 instead of 1
• Assuming XPath returns all matching elements
• Ignoring the class attribute filter

4. You wrote this code but it throws a NoSuchElementException. What is the likely error?

WebElement button = driver.findElement(By.xpath("//button[text()='Submit']"));
button.click();

The HTML is:

<button id='submitBtn'>Submit</button>

medium

A. The button element is inside an iframe and not switched to

B. The XPath is missing the button's id attribute

C. XPath is case-sensitive and 'Submit' text does not match

D. The button is disabled and cannot be clicked

Solution

1. Step 1: Check XPath correctness

   The XPath //button[text()='Submit'] matches the button text exactly, which is correct here.

2. Step 2: Consider common Selenium issues

   If the element is inside an iframe, Selenium cannot find it unless switched to that iframe first. This causes NoSuchElementException.

3. Final Answer:

   The button element is inside an iframe and not switched to -> Option A

4. Quick Check:

   NoSuchElementException often means iframe switch missing [OK]

Hint: Check if element is inside iframe before findElement [OK]

Common Mistakes:

• Assuming XPath text match is case-insensitive
• Ignoring iframe context
• Thinking disabled buttons cause NoSuchElementException

5. You want to find an input field that has either name='email' or placeholder='Email'. Which XPath expression should you use with findElement?

hard

A. //input[@name='email' | @placeholder='Email']

B. //input[@name='email' or @placeholder='Email']

C. //input[contains(@name, 'email') or contains(@placeholder, 'Email')]

D. //input[@name='email' and @placeholder='Email']

Solution

1. Step 1: Understand the requirement

   You want to find an input element that matches either condition: name='email' OR placeholder='Email'.

2. Step 2: Analyze XPath options

   //input[@name='email' or @placeholder='Email'] uses the correct XPath OR operator or between attribute checks. //input[@name='email' and @placeholder='Email'] uses and which requires both attributes. //input[contains(@name, 'email') or contains(@placeholder, 'Email')] uses contains which is broader but acceptable, but the question asks exact match. //input[@name='email' | @placeholder='Email'] uses invalid XPath syntax with | inside predicate.

3. Final Answer:

   //input[@name='email' or @placeholder='Email'] -> Option B

4. Quick Check:

   Use 'or' inside XPath predicate for either condition [OK]

Hint: Use 'or' inside XPath brackets for multiple attribute options [OK]

Common Mistakes:

• Using 'and' instead of 'or' for either condition
• Using invalid XPath operators like '|' inside predicates
• Confusing contains() with exact match