Base test class pattern in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of Base Test Class Setup

Consider the following Java Selenium base test class snippet. What will be the output when the test method runs?

Selenium Java

public class BaseTest {
    protected WebDriver driver;

    @BeforeEach
    public void setUp() {
        System.out.println("Setup started");
        driver = new ChromeDriver();
        driver.get("https://example.com");
        System.out.println("Setup completed");
    }

    @AfterEach
    public void tearDown() {
        driver.quit();
        System.out.println("Driver closed");
    }
}

public class SampleTest extends BaseTest {
    @Test
    public void testTitle() {
        System.out.println(driver.getTitle());
    }
}

A

Example Domain
Setup started
Setup completed
Driver closed

B

Setup started
Example Domain
Setup completed
Driver closed

C

Setup started
Setup completed
Driver closed
Example Domain

D

Setup started
Setup completed
Example Domain
Driver closed

💡 Hint

Remember the order of execution for @BeforeEach, test method, and @AfterEach in JUnit.

The @BeforeEach method runs first, printing 'Setup started' and 'Setup completed'. Then the test method runs, printing the page title 'Example Domain'. Finally, @AfterEach runs, printing 'Driver closed'.

❓ assertion

intermediate

Correct Assertion in Base Test Class

In a base test class, which assertion correctly verifies that the page title contains the word "Example" after navigation?

Selenium Java

public class BaseTest {
    protected WebDriver driver;

    @BeforeEach
    public void setUp() {
        driver = new ChromeDriver();
        driver.get("https://example.com");
    }
}

A assertNull(driver.getTitle());

B assertTrue(driver.getTitle().contains("Example"));

C assertFalse(driver.getTitle().contains("Example"));

D assertEquals(driver.getTitle(), "Example");

💡 Hint

Check which assertion matches the requirement to verify the title contains a substring.

assertTrue with contains("Example") correctly checks if the title includes the word 'Example'. assertEquals would fail because the full title is not exactly 'Example'.

🔧 Debug

advanced

Identify the Bug in Base Test Class Setup

What is the main issue in this base test class setup code that causes tests to fail intermittently?

Selenium Java

public class BaseTest {
    protected WebDriver driver;

    @BeforeEach
    public void setUp() {
        driver = new ChromeDriver();
        driver.get("https://example.com");
    }

    @AfterEach
    public void tearDown() {
        driver.close();
    }
}

A Missing @Test annotation on setUp method causes it not to run.

B Not initializing driver in the constructor causes NullPointerException.

C Using driver.close() instead of driver.quit() causes the browser process to remain open, leading to resource leaks.

D Using driver.quit() in tearDown causes the browser to close too early.

💡 Hint

Consider the difference between driver.close() and driver.quit() in Selenium.

driver.close() closes only the current window but leaves the browser process running. driver.quit() closes all windows and ends the browser process, preventing resource leaks.

❓ framework

advanced

Best Practice for WebDriver Initialization in Base Test Class

Which approach is best for initializing WebDriver in a base test class to support multiple browsers?

A Use a factory method that reads browser type from a config file and returns the appropriate WebDriver instance.

B Hardcode ChromeDriver initialization in the base class constructor.

C Initialize WebDriver in each test method separately for flexibility.

D Use a static WebDriver instance shared across all tests without reinitialization.

💡 Hint

Think about maintainability and flexibility for running tests on different browsers.

A factory method reading from config allows easy switching between browsers without code changes. Hardcoding or static instances reduce flexibility and can cause test interference.

🧠 Conceptual

expert

Purpose of Base Test Class in Selenium Framework

What is the primary purpose of using a base test class pattern in Selenium test automation?

A To centralize common setup and teardown code, reducing duplication and improving maintainability.

B To write all test cases in a single class for simplicity.

C To avoid using any test framework annotations like @BeforeEach or @AfterEach.

D To force all tests to run sequentially without parallel execution.

💡 Hint

Think about how base classes help organize repeated code.

Base test classes hold shared setup and cleanup logic so individual test classes can focus on test logic, avoiding code repetition and easing maintenance.