Selenium WebDriver Action Methods for Reusable Automation Code (Java)

Why Action Methods Matter in Selenium Automation

One of the most common mistakes beginners make in Selenium automation is writing long, linear test scripts. These scripts work initially but quickly become hard to maintain, duplicate-heavy, and fragile as the test suite grows.

A better approach is to design reusable action methods that encapsulate user interactions such as:

• Opening a page

• Entering text

• Clicking buttons

• Selecting options

This concept forms the foundation of maintainable automation frameworks and is a stepping stone toward Page Object Model (POM).

---

What Are Action Methods?

Action methods are small, reusable functions that perform a single UI interaction or business action.

Example:

Instead of repeating login steps in every test:

driver.findElement(By.id("username")).sendKeys("user");
driver.findElement(By.id("password")).sendKeys("pass");
driver.findElement(By.id("login")).click();

You create a reusable method:

login("user", "pass");

This method can then be reused across multiple test cases.

---

Benefits of Using Action Methods

✔ Code reusability across test cases
✔ Better readability and cleaner test scripts
✔ Easier maintenance when UI changes
✔ Foundation for Page Object Model
✔ Faster test development over time

---

Sample Selenium Program Using Reusable Action Methods

Below is a simple demonstration using Selenium WebDriver with Java and JUnit, showing how action methods can be reused across multiple test scenarios.

Key Concepts Demonstrated

• Centralized browser actions

• Reusable UI interaction methods

• Multiple test scenarios using the same actions

---

Selenium WebDriver Action Methods Example (Java)

package com.techlistic.tute;

import org.junit.Assert;
import org.junit.Test;
import org.openqa.selenium.*;
import org.openqa.selenium.firefox.FirefoxDriver;

public class WebdriverActionMethods {

    private WebDriver driver = new FirefoxDriver();
    private String browserUrl = "http://www.toolsqa.com/automation-practice-form/";
    private String userName = "Mark";

    @Test
    public void testScenarioOne() {
        openURL(browserUrl);
        clickOnLinkTest();
        enterFirstName(userName);
        clickSubmit();
    }

    @Test
    public void testScenarioTwo() {
        openURL(browserUrl);
        clickOnLinkTest();
        navigateBackward();
        enterFirstName("John");
        clickingRadioButton();
        selectProfession();
        clickSubmit();

        String expectedTitle = "Selenium | Home";
        Assert.assertEquals(expectedTitle, driver.getTitle());
    }

    /* ---------------- Reusable Action Methods ---------------- */

    public void openURL(String url) {
        driver.get(url);
    }

    public void clickOnLinkTest() {
        driver.findElement(By.linkText("Link Test")).click();
    }

    public void navigateBackward() {
        driver.navigate().back();
    }

    public void enterFirstName(String name) {
        WebElement firstName = driver.findElement(By.name("firstname"));
        firstName.clear();
        firstName.sendKeys(name);
    }

    public void clickingRadioButton() {
        driver.findElement(By.id("sex-1")).click();
    }

    public void selectProfession() {
        driver.findElement(By.name("profession")).click();
    }

    public void clickSubmit() {
        driver.findElement(By.name("submit")).click();
    }
}

---

Where Should Action Methods Live?

In real-world frameworks, action methods should not live inside test classes.

Recommended Structure

src
 ├── pages
 │    └── CommonActions.java
 ├── tests
 │    └── LoginTests.java

Example Usage

CommonActions common = new CommonActions(driver);
common.openURL("https://www.techlistic.com");

This keeps your test logic clean and your UI logic centralized.

---

Action Methods vs Page Object Model (POM)

Action Methods	Page Object Model
UI-focused	Page-centric
Good for beginners	Industry standard
Procedural	Object-oriented
Easy to learn	Scales better

Action methods are the gateway to POM, not a replacement.

---

Best Practices for Action Methods

• Keep methods small and focused
• Avoid assertions inside action methods
• Pass test data as parameters
• Never hardcode locators in tests
• Combine with waits for stability

---

What to Learn Next?

To take this approach further, explore:

• Selenium Page Object Model (POM)
• Selenium with TestNG
• Selenium Practice Assignments

---

Final Thoughts

Reusable action methods are a fundamental automation design skill. They help beginners write cleaner tests and prepare engineers for scalable enterprise automation frameworks.

Once mastered, transitioning to Page Object Model and hybrid frameworks becomes natural.

Visual Testing with Selenium  << Previous  |  Next >> Selenium Page Object Model(POM)