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.

Practice

1. What is the main purpose of using a Base Test Class in Selenium Java testing?

easy

A. To share common setup and cleanup code across multiple test classes

B. To write all test cases in a single class

C. To avoid using WebDriver in tests

D. To make tests run slower for debugging

Solution

1. Step 1: Understand the role of a base test class

   A base test class contains common setup and cleanup methods that multiple test classes can reuse.

2. Step 2: Identify the benefit of code reuse

   Sharing setup code avoids duplication and keeps tests organized and maintainable.

3. Final Answer:

   To share common setup and cleanup code across multiple test classes -> Option A

4. Quick Check:

   Base test class = shared setup/cleanup [OK]

Hint: Base class holds shared setup and teardown code [OK]

Common Mistakes:

• Thinking base class holds all tests
• Ignoring code reuse benefits
• Confusing base class with utility classes

2. Which of the following is the correct way to declare a base test class in Java for Selenium tests?

easy

A. public BaseTest { WebDriver driver; void setup() { } }

B. class BaseTest { void setup() { WebDriver driver = new WebDriver(); } }

C. public class BaseTest extends WebDriver { void setup() { } }

D. public class BaseTest { WebDriver driver; @BeforeEach void setup() { /* init driver */ } }

Solution

1. Step 1: Check Java class declaration syntax

   public class BaseTest { WebDriver driver; @BeforeEach void setup() { /* init driver */ } } correctly declares a public class with a WebDriver field and a setup method annotated with @BeforeEach.

2. Step 2: Identify errors in other options

   class BaseTest { void setup() { WebDriver driver = new WebDriver(); } } misses access modifiers and uses local driver variable incorrectly. public BaseTest { WebDriver driver; void setup() { } } lacks 'class' keyword. public class BaseTest extends WebDriver { void setup() { } } wrongly extends WebDriver, which is an interface.

3. Final Answer:

   public class BaseTest { WebDriver driver; @BeforeEach void setup() { /* init driver */ } } -> Option D

4. Quick Check:

   Correct class syntax with setup method = public class BaseTest { WebDriver driver; @BeforeEach void setup() { /* init driver */ } } [OK]

Hint: Look for public class with WebDriver and @BeforeEach setup [OK]

Common Mistakes:

• Missing 'public' keyword
• Incorrect class declaration syntax
• Extending WebDriver interface wrongly

3. Given the following base test class and child test class, what will be printed when running ChildTest.testExample()?

public class BaseTest {
    WebDriver driver;
    @BeforeEach
    void setup() {
        driver = new ChromeDriver();
        System.out.println("Setup done");
    }
    @AfterEach
    void teardown() {
        driver.quit();
        System.out.println("Teardown done");
    }
}

public class ChildTest extends BaseTest {
    @Test
    void testExample() {
        System.out.println("Test running");
    }
}

medium

A. Test running
Setup done
Teardown done

B. Setup done
Test running
Teardown done

C. Setup done
Teardown done
Test running

D. Test running
Teardown done
Setup done

Solution

1. Step 1: Understand JUnit lifecycle with base class

   @BeforeEach runs before each test method, @AfterEach runs after. ChildTest inherits these methods.

2. Step 2: Trace the output order

   First "Setup done" prints from setup(), then "Test running" from testExample(), finally "Teardown done" from teardown().

3. Final Answer:

   Setup done Test running Teardown done -> Option B

4. Quick Check:

   @BeforeEach -> test -> @AfterEach = Setup done Test running Teardown done [OK]

Hint: Remember: setup before test, teardown after test [OK]

Common Mistakes:

• Assuming setup runs after test
• Ignoring inheritance of setup/teardown
• Mixing order of print statements

4. Identify the error in this base test class code snippet:

public class BaseTest {
    WebDriver driver;
    @BeforeEach
    void setup() {
        driver = new ChromeDriver();
    }
    @AfterEach
    void teardown() {
        driver.close();
    }
}

medium

A. Using driver.close() instead of driver.quit() in teardown

B. Missing public keyword in class declaration

C. Not initializing WebDriver in setup method

D. Using @BeforeEach instead of @BeforeAll

Solution

1. Step 1: Understand difference between driver.close() and driver.quit()

   driver.close() closes current window, driver.quit() closes all windows and ends session.

2. Step 2: Identify best practice for cleanup

   In teardown, driver.quit() is preferred to fully close browser and free resources.

3. Final Answer:

   Using driver.close() instead of driver.quit() in teardown -> Option A

4. Quick Check:

   Proper cleanup uses driver.quit() [OK]

Hint: Use driver.quit() to fully close browser in teardown [OK]

Common Mistakes:

• Confusing driver.close() with driver.quit()
• Forgetting to quit WebDriver session
• Assuming driver.close() frees all resources

5. You want to create a base test class that initializes WebDriver only once before all tests run and quits it after all tests finish. Which JUnit 5 annotations should you use in the base class for setup and teardown methods?

hard

A. @BeforeAll for setup and @AfterEach for teardown with static setup only

B. @BeforeEach for setup and @AfterEach for teardown with instance methods

C. @BeforeAll for setup and @AfterAll for teardown with static methods

D. @BeforeEach for setup and @AfterAll for teardown with instance teardown

Solution

1. Step 1: Understand JUnit 5 lifecycle annotations

   @BeforeAll and @AfterAll run once before and after all tests; methods must be static by default.

2. Step 2: Match requirement to annotations

   To initialize WebDriver once before all tests and quit after all tests, use @BeforeAll and @AfterAll with static methods.

3. Final Answer:

   @BeforeAll for setup and @AfterAll for teardown with static methods -> Option C

4. Quick Check:

   One-time setup/teardown = @BeforeAll/@AfterAll static [OK]

Hint: Use @BeforeAll/@AfterAll static for one-time setup/teardown [OK]

Common Mistakes:

• Using @BeforeEach/@AfterEach for one-time setup
• Not making @BeforeAll/@AfterAll methods static
• Mixing instance and static lifecycle methods