Logging test steps in Selenium Java

Introduction

Logging test steps helps you see what your test is doing. It makes finding problems easier.

When you want to know which part of the test is running.

When a test fails and you want to find out why.

When you share test results with your team.

When you want to keep a record of test actions for later review.

Syntax

Selenium Java

Logger logger = Logger.getLogger(ClassName.class.getName());
logger.info("Your message here");

Use Logger from java.util.logging or a logging library like Log4j.

The info method logs normal messages about test steps.

Examples

Logs a message that the test is starting.

Selenium Java

Logger logger = Logger.getLogger(MyTest.class.getName());
logger.info("Starting test");

Logs a warning message if something might go wrong.

Selenium Java

logger.warning("This step might fail");

Logs a severe error message when the test fails.

Selenium Java

logger.severe("Test failed due to error");

Sample Program

This program logs each step of a simple Selenium test: starting, opening browser, navigating, closing browser, and finishing.

Selenium Java

import java.util.logging.Logger;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;

public class LoggingTestSteps {
    private static final Logger logger = Logger.getLogger(LoggingTestSteps.class.getName());

    public static void main(String[] args) {
        logger.info("Test started");
        System.setProperty("webdriver.chrome.driver", "path/to/chromedriver");
        WebDriver driver = new ChromeDriver();
        logger.info("Browser opened");
        driver.get("https://example.com");
        logger.info("Navigated to example.com");
        driver.quit();
        logger.info("Browser closed");
        logger.info("Test finished");
    }
}

Important Notes

Make sure the logging level is set to show info messages.

Replace path/to/chromedriver with the actual path on your machine.

Logging helps track what your test does step-by-step.

Summary

Logging shows what your test is doing.

Use Logger to add messages in your test code.

Logs help find and fix test problems faster.