WebDriver setup (ChromeDriver) in Selenium Java - Test Execution Trace

Test Overview

This test sets up the Chrome WebDriver, opens the Chrome browser, and verifies that the browser window is opened successfully.

Test Code - JUnit 5 with Selenium

Selenium Java

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.junit.jupiter.api.AfterEach;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.assertNotNull;

public class ChromeDriverSetupTest {
    private WebDriver driver;

    @BeforeEach
    public void setUp() {
        // Set the path to chromedriver executable if needed
        // System.setProperty("webdriver.chrome.driver", "/path/to/chromedriver");
        driver = new ChromeDriver();
    }

    @Test
    public void testChromeDriverSetup() {
        driver.get("about:blank");
        assertNotNull(driver.getWindowHandle(), "Browser window should be opened");
    }

    @AfterEach
    public void tearDown() {
        if (driver != null) {
            driver.quit();
        }
    }
}

Execution Trace - 4 Steps

Step	Action	System State	Assertion	Result
1	Initialize ChromeDriver instance	Chrome browser process starts but no page loaded yet	-	PASS
2	Navigate to about:blank page	Chrome browser opens a blank page	-	PASS
3	Get window handle to verify browser window is opened	Browser window handle is retrieved	Assert that window handle is not null	PASS
4	Close the browser and quit driver	Browser window closes and driver quits	-	PASS

Failure Scenario

Failing Condition: ChromeDriver executable is not found or not compatible

Execution Trace Quiz - 3 Questions

What is the purpose of calling driver.get("about:blank") in this test?

A To close the browser window

B To open a blank page and initialize the browser window

C To set the path for ChromeDriver

D To check if the driver is null

Key Result

Always ensure the ChromeDriver executable path is correctly set before initializing the ChromeDriver to avoid setup failures.