XML and HTML reports in JUnit - Test Execution Trace

Test Overview

This test runs a simple JUnit test case and generates both XML and HTML reports. It verifies that the test passes and that the reports are created successfully.

Test Code - JUnit 5

JUnit

import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.assertEquals;

public class SimpleTest {
    @Test
    public void additionTest() {
        assertEquals(4, 2 + 2, "2 + 2 should equal 4");
    }
}

// To generate reports, run tests with Maven or Gradle configured to produce surefire reports.
// Example Maven command: mvn test
// XML reports are generated in target/surefire-reports/
// HTML reports can be generated using plugins like surefire-report-plugin.

Execution Trace - 5 Steps

Step	Action	System State	Assertion	Result
1	Test runner starts and loads SimpleTest class	JUnit test environment initialized	—	PASS
2	Runs additionTest method	Executing test method additionTest	assertEquals(4, 2 + 2)	PASS
3	Test runner completes execution	Test finished with all tests passing	—	PASS
4	JUnit generates XML report in target/surefire-reports/TEST-SimpleTest.xml	XML report file created with test results	XML report contains test case result with status 'passed'	PASS
5	HTML report generated using surefire-report-plugin	HTML report file created in target/site/surefire-report.html	HTML report displays test summary with passed test	PASS

Failure Scenario

Failing Condition: Test assertion fails or report generation fails

Execution Trace Quiz - 3 Questions

What does the XML report generated by JUnit contain?

A Source code of the test class

B Only the test method names without results

C Test case results including pass/fail status

D Compiled bytecode of the tests

Key Result

Always verify that your test assertions are correct and that your build tool is properly configured to generate reports. This helps you quickly identify test results and share them with your team.

Practice

1. What is the main purpose of XML reports in JUnit testing?

easy

A. To store test results in a structured format for tools to read

B. To display test results directly in a web browser

C. To run tests faster by using XML files

D. To write test cases in XML syntax

Solution

1. Step 1: Understand XML report role

   XML reports save test results in a structured way that other tools can process.

2. Step 2: Compare with other options

   HTML reports display results in browsers, not XML. XML does not speed tests or write test cases.

3. Final Answer:

   To store test results in a structured format for tools to read -> Option A

4. Quick Check:

   XML reports = structured data storage [OK]

Hint: XML = structured data for tools, not direct display [OK]

Common Mistakes:

• Confusing XML reports with HTML display
• Thinking XML speeds up test execution
• Assuming tests are written in XML

2. Which Maven command generates both XML and HTML reports for JUnit tests?

easy

A. mvn test -DreportFormat=xml,html

B. mvn generate-reports

C. mvn surefire-report:report

D. mvn clean install

Solution

1. Step 1: Identify Maven reporting plugin

   The Surefire Report plugin generates XML and HTML reports after tests run.

2. Step 2: Check other commands

   "mvn clean install" runs build and tests but does not generate reports alone. Others are invalid commands.

3. Final Answer:

   mvn surefire-report:report -> Option C

4. Quick Check:

   Surefire report plugin = XML + HTML reports [OK]

Hint: Surefire plugin command generates reports, not just test run [OK]

Common Mistakes:

• Using 'mvn clean install' expecting reports
• Trying invalid Maven commands
• Confusing report generation with test execution

3. Given this snippet from a JUnit XML report:

<testcase classname="CalculatorTest" name="testAdd" time="0.005"/>

What does the attribute time="0.005" represent?

medium

A. The time in seconds the test took to run

B. The timeout limit for the test

C. The number of assertions in the test

D. The priority level of the test

Solution

1. Step 1: Understand XML attribute 'time'

   The 'time' attribute records how long the test took to execute, in seconds.

2. Step 2: Eliminate other meanings

   Timeout is set elsewhere, assertions count is not stored here, and priority is unrelated.

3. Final Answer:

   The time in seconds the test took to run -> Option A

4. Quick Check:

   time attribute = execution duration [OK]

Hint: time attribute always means test duration in seconds [OK]

Common Mistakes:

• Confusing time with timeout limit
• Thinking time counts assertions
• Assuming time is test priority

4. You run JUnit tests with Maven but the HTML report is missing. Which is the most likely cause?

medium

A. The tests did not run due to compilation errors

B. The Surefire plugin is not configured to generate reports

C. The XML report file is corrupted

D. The HTML report is generated only for failed tests

Solution

1. Step 1: Check report generation setup

   If Surefire plugin is not configured properly, no reports are created.

2. Step 2: Analyze other options

   Compilation errors stop tests but usually show errors; corrupted XML won't prevent HTML generation if configured; HTML reports show all tests, not just failures.

3. Final Answer:

   The Surefire plugin is not configured to generate reports -> Option B

4. Quick Check:

   Missing HTML report = plugin config issue [OK]

Hint: Check Surefire plugin config if reports are missing [OK]

Common Mistakes:

• Assuming HTML reports only for failed tests
• Ignoring plugin configuration
• Blaming XML corruption without evidence

5. You want to customize the JUnit HTML report to include test categories and better styling. Which approach is best?

hard

A. Edit the XML report files directly before viewing

B. Use a different testing framework that supports HTML styling

C. Change the test method names to include categories

D. Modify the XSLT files used to transform XML to HTML

Solution

1. Step 1: Understand report generation process

   JUnit XML reports are transformed to HTML using XSLT stylesheets, which control layout and content.

2. Step 2: Evaluate customization options

   Editing XML directly is impractical; changing test names is limited; switching frameworks is unnecessary if customization is possible.

3. Final Answer:

   Modify the XSLT files used to transform XML to HTML -> Option D

4. Quick Check:

   Customize HTML via XSLT transformation [OK]

Hint: Edit XSLT to customize HTML report content and style [OK]

Common Mistakes:

• Trying to edit XML reports directly
• Relying on test names for report styling
• Switching frameworks unnecessarily