Utility classes in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium utility method?

Consider the following Java utility method that waits for an element to be visible. What will be the output if the element is not found within the timeout?

Selenium Java

public static boolean waitForElementVisible(WebDriver driver, By locator, int timeoutSeconds) {
    try {
        WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(timeoutSeconds));
        wait.until(ExpectedConditions.visibilityOfElementLocated(locator));
        return true;
    } catch (TimeoutException e) {
        return false;
    }
}

// Called as: waitForElementVisible(driver, By.id("nonexistent"), 5);

A Returns false after 5 seconds timeout

B Throws TimeoutException immediately

C Returns true immediately

D Throws NoSuchElementException immediately

💡 Hint

Think about how WebDriverWait handles waiting and exceptions.

The method uses WebDriverWait with ExpectedConditions.visibilityOfElementLocated. If the element is not found within the timeout, a TimeoutException is caught and the method returns false.

❓ assertion

intermediate

Which assertion correctly verifies a page title using a utility method?

Given a utility method getPageTitle(WebDriver driver) that returns the current page title, which assertion correctly checks that the title equals "Home Page"?

Selenium Java

public static String getPageTitle(WebDriver driver) {
    return driver.getTitle();
}

A assertEquals("Home Page", getPageTitle(driver));

B assertTrue(getPageTitle(driver) == "Home Page");

C assertFalse(getPageTitle(driver).equals("Home Page"));

D assertNotNull(getPageTitle(driver));

💡 Hint

Use the correct assertion method for string equality.

assertEquals compares string values correctly. Using == compares references, which is incorrect for strings in Java.

❓ locator

advanced

Which locator strategy is best for a utility method to find a button by its visible text?

You want to write a utility method that clicks a button by its visible text. Which locator is the best choice?

A By.className("btn-primary")

B By.id("submitBtn")

C By.cssSelector("button.submit")

D By.xpath("//button[text()='Submit']")

💡 Hint

The button text is unique but no id or class is guaranteed.

Using XPath with the exact button text ensures the utility method finds the button by visible text reliably.

🔧 Debug

advanced

Why does this utility method throw a NullPointerException?

Analyze the following utility method. Why does it throw NullPointerException sometimes?

Selenium Java

public static void clickElement(WebDriver driver, By locator) {
    WebElement element = driver.findElement(locator);
    if (element.isDisplayed()) {
        element.click();
    }
}

A element is null if not found, causing NullPointerException on isDisplayed()

B findElement throws NoSuchElementException if element not found, not NullPointerException

C click() throws NullPointerException if element is not clickable

D driver is null causing NullPointerException

💡 Hint

Check what findElement returns if no element matches the locator.

findElement throws NoSuchElementException if element not found; it never returns null. NullPointerException is unlikely here unless driver is null.

❓ framework

expert

Which design best improves reusability of Selenium utility classes?

You want to design a Selenium utility class for common actions like clicking, typing, and waiting. Which design approach best improves reusability and maintainability?

A Create utility methods inside each test class separately for better context

B Create instance methods in a utility class that stores WebDriver as a field initialized in constructor

C Create static methods in a final utility class that accept WebDriver and locators as parameters

D Create utility methods that extend WebDriver class directly

💡 Hint

Think about how utility classes are commonly designed for easy use across tests.

Static methods in a final utility class allow easy reuse without needing to instantiate objects, improving maintainability and reducing boilerplate.

Practice

1. What is the main purpose of a utility class in Selenium Java testing?

easy

A. To define test case steps in detail

B. To store test data in variables

C. To create WebDriver instances for each test

D. To provide reusable static methods for common tasks

Solution

1. Step 1: Understand utility class role

   Utility classes contain static methods to reuse code easily across tests.

2. Step 2: Compare options with utility class purpose

   Only To provide reusable static methods for common tasks describes reusable static methods, which is the utility class purpose.

3. Final Answer:

   To provide reusable static methods for common tasks -> Option D

4. Quick Check:

   Utility class = reusable static methods [OK]

Hint: Utility classes hold static helpers for reuse [OK]

Common Mistakes:

• Confusing utility class with test data storage
• Thinking utility class creates WebDriver instances
• Mixing utility class with test step definitions

2. Which of the following is the correct way to declare a utility method in Java?

easy

A. public static void openBrowser() {}

B. public void openBrowser() {}

C. void openBrowser() {}

D. static openBrowser() {}

Solution

1. Step 1: Recall utility method syntax

   Utility methods are static so they can be called without creating an object.

2. Step 2: Check each option's syntax

   public static void openBrowser() {} correctly declares a public static method with return type void.

3. Final Answer:

   public static void openBrowser() {} -> Option A

4. Quick Check:

   Utility method = public static method [OK]

Hint: Utility methods must be static for easy access [OK]

Common Mistakes:

• Omitting static keyword
• Missing return type
• Incorrect method declaration syntax

3. Given this utility method:

public static String getPageTitle(WebDriver driver) {
    return driver.getTitle();
}

What will be the output if the current page title is "Home Page"?

medium

A. Compilation error

B. null

C. "Home Page"

D. driver.getTitle()

Solution

1. Step 1: Understand method behavior

   The method returns the page title by calling driver.getTitle().

2. Step 2: Check given page title

   The page title is "Home Page", so the method returns this string.

3. Final Answer:

   "Home Page" -> Option C

4. Quick Check:

   Method returns page title string [OK]

Hint: Method returns driver.getTitle() string [OK]

Common Mistakes:

• Confusing method return with method name
• Expecting null instead of actual title
• Assuming syntax error without checking code

4. Identify the error in this utility class method:

public static void clickElement(WebElement element) {
    element.click;
}

medium

A. Missing parentheses after click method

B. WebElement cannot be passed as parameter

C. Method should return boolean

D. Static keyword is not allowed here

Solution

1. Step 1: Check method syntax

   The method calls element.click but misses parentheses, which is invalid syntax.

2. Step 2: Validate other options

   Passing WebElement is valid, return type void is fine, static allowed in utility methods.

3. Final Answer:

   Missing parentheses after click method -> Option A

4. Quick Check:

   Method call needs () after method name [OK]

Hint: Method calls need parentheses () [OK]

Common Mistakes:

• Forgetting parentheses on method calls
• Thinking WebElement can't be parameter
• Assuming static keyword causes error

5. You want to create a utility class method that waits for an element to be visible before clicking it. Which approach is best?

hard

A. Add wait logic inside each test instead of utility method

B. Create a static method that uses WebDriverWait and then clicks the element

C. Create a non-static method that clicks element immediately without wait

D. Use Thread.sleep() inside utility method before clicking

Solution

1. Step 1: Understand utility method purpose

   Utility methods should provide reusable, clean code for common tasks like waiting and clicking.

2. Step 2: Evaluate options for best practice

   Create a static method that uses WebDriverWait and then clicks the element uses static method with WebDriverWait, which is efficient and reusable. Others are less reliable or not reusable.

3. Final Answer:

   Create a static method that uses WebDriverWait and then clicks the element -> Option B

4. Quick Check:

   Use static method with explicit wait [OK]

Hint: Use static method with WebDriverWait for reliable clicks [OK]

Common Mistakes:

• Using Thread.sleep() causing slow tests
• Not using static method for utility
• Putting wait logic inside tests, not utility