Logging test steps in Selenium Java - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of logging test steps in Selenium tests?

Logging test steps helps track what actions were performed during the test. It makes it easier to understand test flow and find where errors happen.

beginner

Which Java class is commonly used for logging in Selenium tests?

The <code>Logger</code> class from <code>java.util.logging</code> or logging frameworks like Log4j are commonly used to log test steps.

beginner

How do you log a simple message in Java using Logger?

You create a Logger instance and call info() method. Example:

Logger logger = Logger.getLogger("MyTest");
logger.info("Step 1: Open browser");

intermediate

Why is logging test steps better than just printing to the console?

Logging frameworks allow controlling log levels, saving logs to files, and formatting messages. Console prints are simple but less flexible and harder to manage.

intermediate

What is a good practice when logging test steps in Selenium?

Log clear, simple messages describing each test action. Include important details like element names or expected results. Avoid logging sensitive data.

What does logging test steps help with in Selenium tests?

A Changing browser settings

B Tracking test actions and debugging errors

C Making tests run faster

D Skipping test steps automatically

Logging test steps helps track what actions were done and makes debugging easier.

Which Java method is used to log an informational message?

A logger.info()

B logger.error()

C logger.debug()

D logger.print()

The info() method logs informational messages.

Why prefer logging frameworks over System.out.println for test steps?

A System.out.println is faster

B Logging frameworks are harder to use

C Logging frameworks offer levels and file output

D System.out.println can save logs to files

Logging frameworks provide control over log levels and can save logs to files.

What should you avoid logging in test steps?

A Expected results

B Test step descriptions

C Element names

D Sensitive data like passwords

Avoid logging sensitive data to protect security.

Which package contains the Logger class used for logging in Java?

A java.util.logging

B java.io

C java.net

D java.sql

The Logger class is in the java.util.logging package.

Explain why logging test steps is important in Selenium automated tests.

Think about how logs help when tests fail.

Describe how to add logging to a Selenium test in Java using the Logger class.

Remember the syntax: Logger.getLogger and logger.info

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