Why Base test class pattern in Selenium Java? - Purpose & Use Cases

The Big Idea

What if you could write your tests once and reuse setup everywhere without repeating yourself?

The Scenario

Imagine you have many test cases for a website, and each test needs to open the browser, log in, and set up the environment manually before running.

You write the same setup code again and again in every test class.

The Problem

This manual way is slow and boring.

It causes mistakes because if you change the setup, you must update every test class separately.

It wastes time and makes tests hard to maintain.

The Solution

The Base test class pattern solves this by putting common setup and cleanup code in one place.

All test classes then inherit from this base class, so they share the same setup automatically.

This makes tests cleaner, faster to write, and easier to update.

Before vs After

✗ Before

public class LoginTest {
  @Before
  public void setup() {
    // open browser
    // login
  }
  @Test
  public void testLogin() {
    // test steps
  }
}

public class SearchTest {
  @Before
  public void setup() {
    // open browser
    // login
  }
  @Test
  public void testSearch() {
    // test steps
  }
}

✓ After

public class BaseTest {
  @Before
  public void setup() {
    // open browser
    // login
  }
}

public class LoginTest extends BaseTest {
  @Test
  public void testLogin() {
    // test steps
  }
}

public class SearchTest extends BaseTest {
  @Test
  public void testSearch() {
    // test steps
  }
}

What It Enables

It enables writing many tests quickly with shared setup, making your testing faster and less error-prone.

Real Life Example

Think of a team testing an online store. Instead of repeating browser setup and login in every test, they use a base test class to handle it once, so they focus on testing features like adding items or checking out.

Key Takeaways

Manual setup in every test class is slow and error-prone.

Base test class centralizes common setup and cleanup code.

Inheritance makes tests cleaner, easier to maintain, and faster to write.