XML and HTML reports in JUnit - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to generate a JUnit XML report file.

JUnit

JUnitCore junit = new JUnitCore();
Result result = junit.run(MyTestClass.class);
File file = new File("test-results.xml");
JUnitResultWriter writer = new JUnitResultWriter(file);
writer.[1](result);

Drag options to blanks, or click blank then click option'

Awrite

Bsave

Coutput

Dprint

Attempts:

3 left

💡 Hint

Common Mistakes

Using save() or print() which are not valid methods for JUnitResultWriter.

Trying to call write() without passing the result object.

The JUnitResultWriter uses the write() method to save the test results to an XML file.

2fill in blank

medium

Complete the code to generate an HTML report from JUnit XML results using the ReportGenerator class.

JUnit

ReportGenerator generator = new ReportGenerator();
generator.setInputFile("test-results.xml");
generator.setOutputDirectory("reports");
generator.[1]();

Drag options to blanks, or click blank then click option'

Agenerate

Bcreate

Cbuild

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Using create() or run() which do not exist in ReportGenerator.

Forgetting to set input or output paths before calling the method.

The ReportGenerator class uses the generate() method to create the HTML report from XML input.

3fill in blank

hard

Fix the error in the XML report generation code by completing the missing method call.

JUnit

JUnitCore junit = new JUnitCore();
Result result = junit.run(MyTests.class);
JUnitXMLReporter reporter = new JUnitXMLReporter();
reporter.[1](result, new File("results.xml"));

Drag options to blanks, or click blank then click option'

AwriteReport

BgenerateReport

CsaveReport

DexportReport

Attempts:

3 left

💡 Hint

Common Mistakes

Using writeReport or saveReport which are not defined methods.

Using exportReport which is not a valid method here.

The correct method to generate the XML report is generateReport(), which takes the test result and output file.

4fill in blank

hard

Fill both blanks to configure the HTML report generator with input XML and output folder.

JUnit

HTMLReportGenerator generator = new HTMLReportGenerator();
generator.[1]("results.xml");
generator.[2]("html-report");

Drag options to blanks, or click blank then click option'

AsetInputFile

BsetSourceFile

CsetOutputDirectory

DsetDestinationFolder

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing input and output methods.

Using setSourceFile or setDestinationFolder which are not standard method names.

Use setInputFile() to specify the XML input and setOutputDirectory() to specify the HTML output folder.

5fill in blank

hard

Fill all three blanks to create a test suite, run it, and generate an XML report file.

JUnit

TestSuite suite = new TestSuite();
suite.addTestSuite(MyTestClass.class);
JUnitCore core = new JUnitCore();
Result result = core.[1](suite);
JUnitXMLWriter writer = new JUnitXMLWriter(new File("[2]"));
writer.[3](result);

Drag options to blanks, or click blank then click option'

Arun

Btest-results.xml

Cwrite

Dexecute

Attempts:

3 left

💡 Hint

Common Mistakes

Using execute() instead of run() to run tests.

Using incorrect file names or method names.

Use run() to execute the suite, specify the XML filename as 'test-results.xml', and write() to save the results.

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