Page class design in Selenium Java - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a WebDriver variable in the page class.

Selenium Java

private [1] driver;

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

AWebDriver

Bdriver

CWebElement

DString

Attempts:

3 left

💡 Hint

Common Mistakes

Using WebElement instead of WebDriver

Using variable name instead of type

Using String type

The WebDriver variable is declared as WebDriver type to control the browser.

2fill in blank

medium

Complete the constructor to initialize the WebDriver variable.

Selenium Java

public LoginPage([1] driver) {
    this.driver = driver;
}

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

AString

BWebDriver

CWebElement

DLoginPage

Attempts:

3 left

💡 Hint

Common Mistakes

Using WebElement as parameter type

Using class name as parameter type

Using String type

The constructor parameter must be of type WebDriver to assign it to the class variable.

3fill in blank

hard

Fix the error in the method to locate the username input field.

Selenium Java

public WebElement getUsernameField() {
    return driver.findElement([1]);
}

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

ABy.id("username")

BBy.name("username")

CBy.xpath("//input[@id='username']")

DBy.className("username")

Attempts:

3 left

💡 Hint

Common Mistakes

Using By.name when the element has an id

Using By.className which may not be unique

Using complex XPath unnecessarily

Using By.id("username") is the most direct and reliable way to locate the username input field by its id attribute.

4fill in blank

hard

Fill both blanks to create a method that clicks the login button and waits for the home page.

Selenium Java

public void clickLogin() {
    driver.findElement([1]).click();
    new WebDriverWait(driver, Duration.ofSeconds(10))
        .until(ExpectedConditions.[2](By.id("homePage")));
}

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

ABy.id("loginBtn")

BvisibilityOfElementLocated

CBy.name("login")

DelementToBeClickable

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong locator for login button

Using elementToBeClickable instead of visibilityOfElementLocated for waiting

Not waiting for the home page element

The login button is located by By.id("loginBtn") and the wait condition is visibilityOfElementLocated to ensure the home page is visible after login.

5fill in blank

hard

Fill all three blanks to create a method that enters username and password, then clicks login.

Selenium Java

public void login(String username, String password) {
    driver.findElement([1]).sendKeys(username);
    driver.findElement([2]).sendKeys(password);
    driver.findElement([3]).click();
}

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

ABy.id("username")

BBy.id("password")

CBy.id("loginBtn")

DBy.name("login")

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong locators for input fields

Using By.name("login") instead of id for login button

Mixing up username and password locators

The username and password fields are located by their ids "username" and "password", and the login button by "loginBtn".

Practice

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

easy

A. To handle API requests

B. To write test assertions directly

C. To group web page elements and actions in one place

D. To manage database connections

Solution

1. Step 1: Understand the role of page classes

   Page classes organize locators and actions related to a specific web page.

2. Step 2: Identify the main purpose

   This organization improves code readability and reuse by keeping page details in one place.

3. Final Answer:

   To group web page elements and actions in one place -> Option C

4. Quick Check:

   Page class purpose = Group elements and actions [OK]

Hint: Page classes group elements and actions per page [OK]

Common Mistakes:

• Confusing page classes with test classes
• Using page classes for database or API logic
• Writing assertions inside page classes

2. Which of the following is the correct way to declare a locator in a Selenium page class using Java?

easy

A. public void submitButton = driver.findElement(By.id("submit"));

B. public String submitButton = "submit";

C. private WebElement submitButton = driver.findElement(By.id("submit"));

D. private By submitButton = By.id("submit");

Solution

1. Step 1: Recall best practice for locators

   Locators should be stored as By objects, not WebElement, to delay element lookup.

2. Step 2: Check each option

   private By submitButton = By.id("submit"); correctly declares a private By locator with By.id("submit").

3. Final Answer:

   private By submitButton = By.id("submit"); -> Option D

4. Quick Check:

   Locators = By objects [OK]

Hint: Use By for locators, not WebElement directly [OK]

Common Mistakes:

• Declaring locators as WebElement fields
• Using public visibility for locators
• Assigning void type to variables

3. Given the following page class snippet, what will loginPage.getTitle() return if the page title is "Welcome Page"?

public class LoginPage {
  private WebDriver driver;
  public LoginPage(WebDriver driver) {
    this.driver = driver;
  }
  public String getTitle() {
    return driver.getTitle();
  }
}

medium

A. "Welcome Page"

B. "Login Page"

C. null

D. Throws NullPointerException

Solution

1. Step 1: Understand getTitle() method

   The method calls driver.getTitle(), which returns the current page title.

2. Step 2: Match with given page title

   The page title is "Welcome Page", so getTitle() returns this string.

3. Final Answer:

   "Welcome Page" -> Option A

4. Quick Check:

   driver.getTitle() = "Welcome Page" [OK]

Hint: driver.getTitle() returns current page title string [OK]

Common Mistakes:

• Assuming getTitle() returns page class name
• Expecting null if not set explicitly
• Confusing with element text retrieval

4. Identify the error in this page class method:

public void clickLogin() {
  WebElement loginBtn = driver.findElement(By.id("login"));
  loginBtn.click();
}

medium

A. No error, method is correct

B. Should store locator as a By field, not find element inside method

C. Missing exception handling for element not found

D. Method should return WebElement instead of void

Solution

1. Step 1: Review locator usage best practice

   Locators should be stored as By fields in the page class, not found inside methods.

2. Step 2: Identify the problem

   Finding element inside method reduces reuse and violates page class design principles.

3. Final Answer:

   Should store locator as a By field, not find element inside method -> Option B

4. Quick Check:

   Locators as By fields = best practice [OK]

Hint: Keep locators as fields, find elements in methods [OK]

Common Mistakes:

• Finding elements repeatedly inside methods
• Ignoring locator reuse
• Assuming exception handling is mandatory here

5. You want to design a page class for a login page with username, password fields, and a login button. Which design approach is best to follow?

hard

A. Store locators as private By fields; create public methods to enter username, enter password, and click login

B. Store WebElement fields publicly and access them directly in tests

C. Write all test steps inside the page class constructor

D. Use static methods only without storing any locators

Solution

1. Step 1: Recall page class design principles

   Locators should be private By fields; actions should be public methods for reuse and encapsulation.

2. Step 2: Evaluate options

   Store locators as private By fields; create public methods to enter username, enter password, and click login follows best practice by separating locators and actions clearly.

3. Final Answer:

   Store locators as private By fields; create public methods to enter username, enter password, and click login -> Option A

4. Quick Check:

   Private locators + public methods = best design [OK]

Hint: Private locators + public action methods = good page class [OK]

Common Mistakes:

• Making locators public and exposing WebElements
• Putting test logic in constructors
• Using static methods without instance context