Logging test steps in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Selenium Java logging code?

Consider the following Selenium Java code snippet that uses java.util.logging.Logger to log test steps. What will be printed to the console?

Selenium Java

import java.util.logging.Logger;
import java.util.logging.Level;

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

    public static void main(String[] args) {
        logger.setLevel(Level.INFO);
        logger.info("Starting test execution");
        logger.warning("This is a warning message");
        logger.severe("This is an error message");
    }
}

A

INFO Starting test execution
WARNING This is a warning message
SEVERE This is an error message

B

INFO: Starting test execution
WARNING: This is a warning message
SEVERE: This is an error message

C

Starting test execution
This is a warning message
This is an error message

D Error: Logger not initialized

💡 Hint

Look at the default format of java.util.logging.Logger output.

The java.util.logging.Logger prints messages with the level name followed by a colon and the message. So info, warning, and severe messages appear with their level labels.

❓ Configuration

intermediate

Which configuration enables detailed logging for Selenium WebDriver in Java?

You want to enable detailed logging for Selenium WebDriver actions in your Java test. Which option correctly sets the logging level to show all messages?

A Logger.getLogger("org.selenium").setLevel(Level.WARNING);

B Logger.getLogger("selenium").setLevel(Level.SEVERE);

C Logger.getLogger("webdriver").setLevel(Level.OFF);

D Logger.getLogger("org.openqa.selenium").setLevel(Level.ALL);

💡 Hint

The Selenium WebDriver logs are under the 'org.openqa.selenium' package.

To see all Selenium WebDriver logs, set the logger for 'org.openqa.selenium' to Level.ALL. Other options either use wrong package names or levels that suppress logs.

🔀 Workflow

advanced

What is the correct order to add logging to Selenium test steps?

Arrange the steps in the correct order to add logging for Selenium test steps in Java.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about initializing logger before using it and logging before and after actions.

First, create the Logger instance. Then log the start, perform actions, and finally log completion.

❓ Troubleshoot

advanced

Why does this Selenium Java test not show any log output?

Given this code snippet, why might no log messages appear on the console? import java.util.logging.Logger; public class Test { private static final Logger logger = Logger.getLogger(Test.class.getName()); public static void main(String[] args) { logger.info("Test started"); } }

A The default logging level is higher than INFO, so INFO messages are not shown

B The main method is not executed

C The code is missing a call to logger.start()

D Logger is not initialized properly, causing no output

💡 Hint

Check the default logging level for java.util.logging.Logger.

By default, the logging level is set to INFO or higher, but sometimes the console handler level is set to WARNING, so INFO messages are not shown unless the handler level is lowered.

✅ Best Practice

expert

Which is the best practice for logging Selenium test steps in Java?

Choose the best practice for logging test steps in Selenium Java tests to ensure clear, maintainable logs.

A Avoid logging to keep tests fast and clean

B Log every single WebDriver command at SEVERE level to catch all errors

C Use descriptive messages with test step details and log at appropriate levels (INFO, WARNING, SEVERE)

D Use System.out.println for all logging to simplify output

💡 Hint

Think about clarity and usefulness of logs for debugging.

Good logging uses descriptive messages and appropriate log levels to help understand test flow and issues. Logging everything as SEVERE or using System.out.println is not recommended.

Practice

1. What is the main purpose of adding logging statements in Selenium Java tests?

easy

A. To make the test run faster

B. To show what the test is doing step-by-step

C. To change the test results

D. To hide errors from the user

Solution

1. Step 1: Understand logging purpose

   Logging records actions during test execution to track progress.

2. Step 2: Identify correct purpose

   Logging helps see what the test does, not speed or hide errors.

3. Final Answer:

   To show what the test is doing step-by-step -> Option B

4. Quick Check:

   Logging = Show test steps [OK]

Hint: Logging tells what happens during tests [OK]

Common Mistakes:

• Thinking logging speeds up tests
• Believing logging changes test results
• Assuming logging hides errors

2. Which of the following is the correct way to create a Logger instance in Selenium Java?

easy

A. Logger logger = Logger.createLogger();

B. Logger logger = new Logger();

C. Logger logger = Logger.getLogger("TestLogger");

D. Logger logger = Logger();

Solution

1. Step 1: Recall Logger creation syntax

   In Java, Logger is created using getLogger with a name string.

2. Step 2: Check options for correct syntax

   Only Logger logger = Logger.getLogger("TestLogger"); uses Logger.getLogger with a string, which is correct.

3. Final Answer:

   Logger logger = Logger.getLogger("TestLogger"); -> Option C

4. Quick Check:

   Logger creation = getLogger("name") [OK]

Hint: Use Logger.getLogger("name") to create logger [OK]

Common Mistakes:

• Trying to instantiate Logger with new
• Using wrong method names like createLogger
• Calling Logger as a function

3. What will be the output in the console after running this code snippet?

Logger logger = Logger.getLogger("TestLogger");
logger.info("Starting test");
logger.warning("Element not found");

medium

A. Error: Logger not initialized

B. Starting test\nElement not found

C. No output

D. INFO: Starting test\nWARNING: Element not found

Solution

1. Step 1: Understand logger methods

   logger.info prints info level messages; logger.warning prints warning level messages.

2. Step 2: Predict console output format

   Output includes level labels INFO and WARNING before messages.

3. Final Answer:

   INFO: Starting test\nWARNING: Element not found -> Option D

4. Quick Check:

   Logger output = Level + message [OK]

Hint: Logger prints level name before message [OK]

Common Mistakes:

• Expecting messages without level labels
• Thinking logger prints nothing by default
• Confusing info and warning outputs

4. Identify the error in this Selenium Java logging code:

Logger logger = Logger.getLogger("TestLogger")
logger.info("Test started");

medium

A. Missing semicolon after getLogger statement

B. Logger cannot be used without import

C. logger.info should be logger.log

D. Logger name must be a class, not a string

Solution

1. Step 1: Check Java syntax

   Java statements must end with a semicolon (;).

2. Step 2: Find missing semicolon

   The first line lacks a semicolon after getLogger call.

3. Final Answer:

   Missing semicolon after getLogger statement -> Option A

4. Quick Check:

   Java lines end with ; [OK]

Hint: Check for missing semicolons in Java code [OK]

Common Mistakes:

• Ignoring missing semicolon errors
• Confusing logger.info with logger.log
• Thinking Logger name must be a class

5. You want to log each step of a Selenium test to help debug failures. Which approach is best to add logging for multiple steps?

hard

A. Create one Logger instance and call logger.info() before each test action

B. Create a new Logger instance before every test step

C. Use System.out.println() instead of Logger for all steps

D. Add logging only after test finishes

Solution

1. Step 1: Understand efficient logging practice

   One Logger instance reused for all steps is efficient and clear.

2. Step 2: Evaluate other options

   Creating many Logger instances wastes resources; System.out.println lacks levels; logging only after test misses step details.

3. Final Answer:

   Create one Logger instance and call logger.info() before each test action -> Option A

4. Quick Check:

   Reuse one Logger, log each step [OK]

Hint: Use one Logger, log before each action [OK]

Common Mistakes:

• Creating multiple Logger instances unnecessarily
• Using print statements instead of Logger
• Logging only at test end