Utility classes in Selenium Java - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a WebDriver instance using a utility class method.

Selenium Java

WebDriver driver = UtilityClass.[1]();

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

AinitializeDriver

BstartSession

ClaunchBrowser

DgetDriver

Attempts:

3 left

💡 Hint

Common Mistakes

Using method names that do not exist in the utility class.

Confusing method names that start a session but do not return the driver.

The utility class method getDriver() is commonly used to return a WebDriver instance.

2fill in blank

medium

Complete the code to wait for an element to be visible using the utility class.

Selenium Java

UtilityClass.[1](driver, By.id("submitBtn"), 10);

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

AwaitForVisibility

BwaitForPresence

CwaitForClickable

DwaitForText

Attempts:

3 left

💡 Hint

Common Mistakes

Using waitForClickable when visibility is required.

Using waitForPresence which waits only for the element to be in the DOM.

The method waitForVisibility waits until the element is visible on the page.

3fill in blank

hard

Fix the error in the utility method call to take a screenshot.

Selenium Java

UtilityClass.[1](driver, "error.png");

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

AtakeScreenshot

BcaptureScreenshot

CcaptureScreen

DtakeScreenShot

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect capitalization in method names.

Using similar but non-existent method names.

The correct method name is takeScreenshot with a lowercase 's' in 'shot'.

4fill in blank

hard

Fill both blanks to create a utility method that returns a list of WebElements by CSS selector.

Selenium Java

public static List<WebElement> [1](WebDriver driver, String selector) {
    return driver.findElements(By.[2](selector));
}

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

AgetElementsByCss

BgetElementsById

CcssSelector

DclassName

Attempts:

3 left

💡 Hint

Common Mistakes

Using By.id or By.className instead of By.cssSelector.

Using method names that do not describe CSS selection.

The method getElementsByCss is a utility method name, and cssSelector is the correct By method to find elements by CSS selector.

5fill in blank

hard

Fill all three blanks to implement a utility method that waits for an element to be clickable and then clicks it.

Selenium Java

public static void [1](WebDriver driver, By locator, int timeout) {
    WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds([2]));
    WebElement element = wait.until(ExpectedConditions.[3](locator));
    element.click();
}

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

AclickWhenReady

Btimeout

CelementToBeClickable

DwaitTime

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong ExpectedConditions methods like visibility instead of clickability.

Using incorrect variable names for timeout.

The method clickWhenReady describes clicking when ready, timeout is the variable for seconds, and elementToBeClickable is the ExpectedConditions method to wait for clickability.

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