Test result publishing in JUnit - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is test result publishing in JUnit?

It is the process of saving and sharing the outcomes of test runs, such as pass or fail status, so others can review and analyze them.

beginner

Why is publishing test results important?

Publishing test results helps teams quickly see if code changes broke anything, supports continuous integration, and improves software quality by making test outcomes visible.

beginner

Which file format does JUnit commonly use to publish test results?

JUnit commonly publishes test results in XML format, which can be read by many tools and CI systems.

intermediate

How can you configure JUnit to publish test results in a build tool like Maven?

In Maven, the surefire plugin runs JUnit tests and automatically generates XML reports in the target/surefire-reports folder.

beginner

What information is typically included in a published JUnit test result report?

Reports usually include the number of tests run, passed, failed, skipped, error messages, and stack traces for failures.

What format does JUnit use to publish test results?

A CSV

B JSON

C XML

D YAML

JUnit test results are commonly published in XML format for compatibility with many tools.

Where does Maven store JUnit test result reports by default?

A target/surefire-reports

B output/test-results

C build/reports

D src/test/reports

Maven's Surefire plugin saves JUnit reports in the target/surefire-reports directory.

Which of the following is NOT typically included in a JUnit test report?

A Number of tests run

B Source code of tests

C Test execution time

D Failure stack traces

JUnit reports do not include the source code of tests, only results and related info.

Why is publishing test results useful in continuous integration?

A To avoid running tests

B To hide test failures

C To slow down the build process

D To share test outcomes with the team

Publishing test results shares outcomes so the team can quickly fix issues.

Which Maven plugin is responsible for running JUnit tests and publishing results?

A surefire

B compiler

C jar

D clean

The Surefire plugin runs tests and generates test result reports.

Explain how JUnit test results are published and why this is important in software development.

Think about how test results help teams catch bugs early.

Describe how you would configure a Maven project to publish JUnit test results.

Focus on the plugin and report location.

Practice

1. What does test result publishing in JUnit primarily show?

easy

A. Whether tests pass or fail

B. The source code of the tests

C. The time taken to write tests

D. The number of test files in the project

Solution

1. Step 1: Understand the purpose of test result publishing

   Test result publishing shows the outcome of running tests, mainly if they pass or fail.

2. Step 2: Identify what is displayed after tests run

   JUnit displays test results to inform developers about test success or failure.

3. Final Answer:

   Whether tests pass or fail -> Option A

4. Quick Check:

   Test result publishing = pass/fail status [OK]

Hint: Test results show pass or fail status [OK]

Common Mistakes:

• Confusing test results with source code
• Thinking test results show test writing time
• Assuming test results count files

2. Which JUnit annotation is used to mark a method as a test so its result can be published?

easy

A. @Test

B. @AfterEach

C. @BeforeAll

D. @Ignore

Solution

1. Step 1: Identify the annotation that marks test methods

   The @Test annotation tells JUnit which methods to run as tests and publish results for.

2. Step 2: Differentiate from other lifecycle annotations

   @BeforeAll and @AfterEach are for setup/cleanup, @Ignore skips tests, so they don't mark tests themselves.

3. Final Answer:

   @Test -> Option A

4. Quick Check:

   Test method annotation = @Test [OK]

Hint: Use @Test to mark test methods [OK]

Common Mistakes:

• Using @BeforeAll or @AfterEach as test markers
• Confusing @Ignore with test execution
• Missing @Test annotation on test methods

3. Given this JUnit test method, what will the test result publishing show?

  @Test
  void testSum() {
    assertEquals(5, 2 + 3);
  }

medium

A. Test fails because 2 + 3 is not 5

B. Test throws an error due to syntax

C. Test passes because 2 + 3 equals 5

D. Test is ignored due to missing annotation

Solution

1. Step 1: Evaluate the assertion in the test method

   The assertion checks if 2 + 3 equals 5, which is true.

2. Step 2: Determine the test outcome based on assertion

   Since the assertion is true, the test passes and JUnit publishes a pass result.

3. Final Answer:

   Test passes because 2 + 3 equals 5 -> Option C

4. Quick Check:

   2 + 3 = 5 means test passes [OK]

Hint: Check if assertion condition is true for pass [OK]

Common Mistakes:

• Assuming 2 + 3 is not 5
• Thinking missing annotation causes ignore here
• Confusing syntax errors with assertion failures

4. This JUnit test method is supposed to check if a list is empty, but the test result publishing shows failure. What is the error?

  @Test
  void testEmptyList() {
    List<String> list = new ArrayList<>();
    assertTrue(list.isEmpty());
  }

medium

A. assertTrue is used incorrectly; should be assertFalse

B. No error; test should pass and publish success

C. The list is not initialized properly

D. Missing import for List causes failure

Solution

1. Step 1: Analyze the list initialization

   The list is created as a new empty ArrayList, so list.isEmpty() returns true.

2. Step 2: Check the assertion logic

   assertTrue(list.isEmpty()) expects true, which matches the empty list state, so the test passes.

3. Final Answer:

   No error; test should pass and publish success -> Option B

4. Quick Check:

   Empty list means assertTrue(list.isEmpty()) passes [OK]

Hint: Empty list means isEmpty() returns true [OK]

Common Mistakes:

• Thinking list is not empty after initialization
• Confusing assertTrue with assertFalse
• Assuming missing imports cause test failure without error

5. You want to publish test results in a JUnit project and generate a report file automatically after tests run. Which approach is best?

hard

A. Add @Report annotation to test classes to auto-generate reports

B. Manually write test results to a file inside each test method

C. Print test results to console and copy them manually to a file

D. Use a build tool like Maven or Gradle with JUnit plugins to generate reports

Solution

1. Step 1: Understand automated test result publishing

   Build tools like Maven or Gradle integrate with JUnit to run tests and generate reports automatically.

2. Step 2: Evaluate other options for report generation

   Manually writing or copying results is error-prone and inefficient; @Report annotation does not exist in JUnit.

3. Final Answer:

   Use a build tool like Maven or Gradle with JUnit plugins to generate reports -> Option D

4. Quick Check:

   Automate reports with build tools [OK]

Hint: Use Maven/Gradle plugins for automatic reports [OK]

Common Mistakes:

• Trying to write results manually inside tests
• Copying console output instead of automating
• Assuming non-existent annotations generate reports