Action methods per page in Selenium Java - Framework Patterns

Framework Mode - Action methods per page

Folder Structure

src
└── test
    └── java
        └── com
            └── example
                ├── pages
                │   ├── LoginPage.java
                │   ├── HomePage.java
                │   └── ProfilePage.java
                ├── tests
                │   ├── LoginTest.java
                │   └── ProfileTest.java
                ├── utils
                │   ├── DriverFactory.java
                │   └── WaitUtils.java
                └── config
                    └── ConfigReader.java

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown (e.g., DriverFactory.java).
• Page Objects Layer: Contains page classes (e.g., LoginPage.java) with locators and action methods that perform user interactions like clicking buttons or entering text.
• Test Layer: Contains test classes (e.g., LoginTest.java) that call page object action methods to perform test scenarios.
• Utilities Layer: Helper classes for waits, logging, or common utilities (e.g., WaitUtils.java).
• Configuration Layer: Reads environment settings, URLs, credentials (e.g., ConfigReader.java).

Configuration Patterns

Use a config.properties file to store environment URLs, browser types, and credentials. Load these in ConfigReader.java. Example:

env.url=https://example.com
browser=chrome
username=testuser
password=secret

DriverFactory reads the browser property to start the correct WebDriver.

Tests use ConfigReader to get URLs and credentials, keeping sensitive data out of code.

Test Reporting and CI/CD Integration

• Use TestNG for running tests and generating HTML reports.
• Integrate with CI tools like Jenkins or GitHub Actions to run tests on code changes.
• Reports show which tests passed or failed, with screenshots on failure.
• Logs from action methods help debug test failures.

Best Practices for Action Methods per Page

• One Action Method per User Interaction: Each method should do one clear action, like clickLoginButton() or enterUsername(String username).
• Use Clear Method Names: Names should describe the action so tests read like a story.
• Keep Locators Private: Locators stay inside the page class; tests never access them directly.
• Return Page Objects When Navigating: If an action leads to a new page, return that page object from the method.
• Use Explicit Waits Inside Actions: Wait for elements to be ready before interacting to avoid flaky tests.

Self Check

Where in this folder structure would you add a new action method clickLogoutButton() for the logout feature?

Key Result

Organize user interactions as clear action methods inside page classes to keep tests readable and maintainable.

Practice

1. What is the main purpose of action methods in a Selenium page object?

easy

A. To represent user actions like clicking or typing on the page

B. To store test data for validation

C. To configure browser settings

D. To generate test reports automatically

Solution

1. Step 1: Understand the role of action methods

   Action methods are designed to perform user interactions such as clicking buttons or entering text.

2. Step 2: Differentiate from other page object responsibilities

   Storing data, configuring browsers, or generating reports are not the role of action methods.

3. Final Answer:

   To represent user actions like clicking or typing on the page -> Option A

4. Quick Check:

   Action methods = user actions [OK]

Hint: Action methods do what a user does on the page [OK]

Common Mistakes:

• Confusing action methods with data storage
• Thinking action methods configure the browser
• Assuming action methods generate reports

2. Which of the following is the correct way to define an action method that clicks a button using Selenium Java?

easy

A. public void clickButton() { driver.findElement(By.id("btn")).getText(); }

B. public void clickButton() { driver.findElement(By.id("btn")).click(); }

C. public void clickButton() { driver.findElement(By.id("btn")).sendKeys(); }

D. public void clickButton() { driver.findElement(By.id("btn")).clear(); }

Solution

1. Step 1: Identify the correct Selenium method for clicking

   The method click() performs a click action on the element.

2. Step 2: Check the other methods

   sendKeys() types text, getText() reads text, and clear() clears input fields.

3. Final Answer:

   public void clickButton() { driver.findElement(By.id("btn")).click(); } -> Option B

4. Quick Check:

   Click action uses click() method [OK]

Hint: Click uses click(), not sendKeys() or getText() [OK]

Common Mistakes:

• Using sendKeys() instead of click() to click
• Calling getText() which only reads text
• Using clear() which clears input fields

3. Given the following action method in a page object:

public void enterUsername(String name) {
    driver.findElement(By.name("username")).sendKeys(name);
}

What will happen when enterUsername("testUser") is called?

medium

A. The text "testUser" will be typed into the username input field

B. The username input field will be cleared

C. An error will occur because sendKeys requires no arguments

D. The username input field will be clicked but not typed

Solution

1. Step 1: Understand sendKeys() usage

   The sendKeys() method types the given string into the located input field.

2. Step 2: Analyze the method call

   Calling enterUsername("testUser") passes "testUser" to sendKeys(), so it types this text.

3. Final Answer:

   The text "testUser" will be typed into the username input field -> Option A

4. Quick Check:

   sendKeys("text") types text [OK]

Hint: sendKeys(text) types text into input fields [OK]

Common Mistakes:

• Thinking sendKeys() clears the field
• Believing sendKeys() takes no arguments
• Confusing click() with sendKeys()

4. Consider this action method:

public void submitForm() {
    driver.findElement(By.id("submitBtn")).click();
    driver.findElement(By.id("submitBtn")).click();
}

What is the issue with this method?

medium

A. It does not locate the submit button correctly

B. It uses an invalid locator syntax

C. It will cause a compilation error due to duplicate lines

D. It clicks the submit button twice unnecessarily

Solution

1. Step 1: Review the method actions

   The method calls click() on the same button twice in a row.

2. Step 2: Understand the impact

   Clicking twice may cause unexpected behavior or duplicate submissions.

3. Final Answer:

   It clicks the submit button twice unnecessarily -> Option D

4. Quick Check:

   Duplicate clicks cause redundant actions [OK]

Hint: Avoid repeating click() on same element twice [OK]

Common Mistakes:

• Thinking duplicate lines cause compile errors
• Assuming locator syntax is wrong
• Believing the button is not found

5. You want to create an action method that selects a checkbox only if it is not already selected. Which of the following is the best implementation?

hard

A. public void selectCheckbox() {
WebElement checkbox = driver.findElement(By.id("agree"));
checkbox.isSelected();
}

B. public void selectCheckbox() {
driver.findElement(By.id("agree")).click();
}

C. public void selectCheckbox() {
WebElement checkbox = driver.findElement(By.id("agree"));
if (!checkbox.isSelected()) {
checkbox.click();
}
}

D. public void selectCheckbox() {
WebElement checkbox = driver.findElement(By.id("agree"));
checkbox.clear();
}

Solution

1. Step 1: Check if checkbox is already selected

   Use isSelected() to verify checkbox state before clicking.

2. Step 2: Click only if not selected

   Clicking only when unchecked prevents unchecking it accidentally.

3. Final Answer:

   public void selectCheckbox() { WebElement checkbox = driver.findElement(By.id("agree")); if (!checkbox.isSelected()) { checkbox.click(); } } -> Option C

4. Quick Check:

   Check isSelected() before click to avoid toggling [OK]

Hint: Click checkbox only if not selected using isSelected() [OK]

Common Mistakes:

• Clicking checkbox without checking state
• Calling isSelected() without action
• Using clear() on checkbox which is invalid