jenkinsci / jenkinsci/junit-plugin

[JENKINS-4951] JUnit report doesn't distinguish between test failures and errors

Open
#846 20 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component:junit-plugin imported-jira-issue priority:critical resolution:unresolved
Dominant language
Java
Stars
87
Forks
351
Avg merge
1d 19h
Merged PRs (30d)
2

Description

The JUnit report produced on processing the XML doesn't distinguish between
JUnit Test Failures and Errors.
The XML looks like this:

The report says:
4 failures
15 tests

If you process the same XML using Ant's junitreport task you get:
Tests Failures Errors
15 3 1


Originally reported by saurabh_arora, imported from: JUnit report doesn't distinguish between test failures and errors
  • status: Reopened
  • priority: Critical
  • component(s): junit-plugin
  • resolution: Unresolved
  • votes: 20
  • watchers: 23
  • imported: 2025-11-26
Raw content of original issue

The JUnit report produced on processing the XML doesn't distinguish between JUnit Test Failures and Errors. The XML looks like this: <testsuite errors="1" failures="3" name="results" tests="15">

The report says: 4 failures 15 tests

If you process the same XML using Ant's junitreport task you get: Tests Failures Errors 15 3 1

  • environment: Platform: All, OS: All
4 attachments

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the JUnit XML processing and report-generation entry points, then trace how the testsuite errors and failures attributes are handled. Add a regression test using the reported XML values and verify that the generated report shows 3 failures and 1 error rather than 4 failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.