XML and HTML reports in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this JUnit XML report snippet?

Given this XML snippet from a JUnit test report, what is the value of the attribute tests in the testsuite element?

JUnit

<testsuite name="CalculatorTests" tests="5" failures="1" errors="0" skipped="0">
  <testcase classname="CalculatorTests" name="testAdd" time="0.01"/>
  <testcase classname="CalculatorTests" name="testSubtract" time="0.01">
    <failure message="expected:&lt;5&gt; but was:&lt;3&gt;" type="AssertionError"/>
  </testcase>
  <testcase classname="CalculatorTests" name="testMultiply" time="0.01"/>
  <testcase classname="CalculatorTests" name="testDivide" time="0.01"/>
  <testcase classname="CalculatorTests" name="testModulo" time="0.01"/>
</testsuite>

A 5

B 4

C 1

D 0

💡 Hint

Look at the tests attribute inside the testsuite tag.

The tests attribute shows the total number of test cases run in the suite. Here, it is set to 5, matching the number of testcase elements.

❓ assertion

intermediate

Which assertion correctly checks if the HTML report contains the summary of failed tests?

You have generated an HTML report from JUnit XML. Which assertion correctly verifies that the report contains the text showing the number of failed tests as 2?

JUnit

String htmlReport = "<html><body><div id='summary'>Tests run: 10, Failures: 2, Errors: 0</div></body></html>";

A assertEquals(htmlReport, "Failures: 2");

B assertTrue(htmlReport.contains("Failures: 2"));

C assertFalse(htmlReport.contains("Failures: 2"));

D assertNull(htmlReport);

💡 Hint

Check if the string contains the expected substring.

The assertion should check that the HTML report string contains the substring "Failures: 2". Option B uses assertTrue with contains(), which is correct.

🔧 Debug

advanced

Why does this JUnit XML report fail to show any test cases in the HTML report?

Given this XML snippet, the generated HTML report shows zero tests run. What is the likely cause?

JUnit

<testsuite name="SampleTests" tests="0" failures="0" errors="0" skipped="0">
</testsuite>

A The <code>tests</code> attribute is zero, so no test cases are recorded.

B The <code>failures</code> attribute should be greater than zero to show tests.

C The <code>skipped</code> attribute must be set to zero explicitly.

D The <code>errors</code> attribute is missing, causing the report to fail.

💡 Hint

Look at the tests attribute value.

If the tests attribute is zero, it means no tests were run or recorded, so the HTML report will show zero tests.

❓ framework

advanced

Which tool is commonly used to convert JUnit XML reports into readable HTML reports?

You want to generate an HTML report from JUnit XML test results. Which tool or plugin is most commonly used for this purpose?

A Mockito Framework

B JUnit Jupiter Engine

C TestNG XML Parser

D Surefire Report Plugin

💡 Hint

Look for a Maven plugin that generates reports.

The Surefire Report Plugin is a Maven plugin that converts JUnit XML results into HTML reports.

🧠 Conceptual

expert

What is the main advantage of using XML reports for automated test results?

Why do automated testing frameworks often output test results in XML format like JUnit XML?

A XML reports reduce the test execution time significantly.

B XML reports are human-readable and require no additional tools to interpret.

C XML reports provide a standardized, machine-readable format that can be easily parsed and transformed into other formats like HTML.

D XML reports automatically fix test failures when parsed.

💡 Hint

Think about why machines prefer XML for data exchange.

XML is a structured, standardized format that tools can parse to generate reports or integrate with other systems. It is not primarily for human reading or performance improvement.

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