jenkinsci / jenkinsci/junit-plugin

[JENKINS-32878] Misleading information if parsing xml report failed

Open
#1,015 0 comments 0 reactions 0 assignees View on GitHub
component:junit-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
87
Forks
351
Avg merge
1d 19h
Merged PRs (30d)
2

Description

When parsing xml report failed with know bug:

java.util.MissingResourceException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages

plugin marks test result as failure and shows output of "failed" test its error message during parsing. This is really confusing. I think that there would be some state like unknow or unreachable and output should not be definitely error message during parsing result xml. Or at least build should faild and inform user that results of his tests was not parsed.

---
Originally reported by lvotypkova, imported from: Misleading information if parsing xml report failed


  • status: Open
  • priority: Minor
  • component(s): junit-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 2
  • imported: 2025-11-26

Raw content of original issue

When parsing xml report failed with know bug:

java.util.MissingResourceException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages

plugin marks test result as failure and shows output of "failed" test its error message during parsing. This is really confusing. I think that there would be some state like unknow or unreachable and output should not be definitely error message during parsing result xml. Or at least build should faild and inform user that results of his tests was not parsed.

Contributor guide

Open the contributing guide

Research direction

Start with the junit-plugin path that parses XML reports and reproduce the MissingResourceException described in the issue. Determine how parsing failures are currently represented and what user-facing result is expected, then add coverage showing that an unparsed report is not presented as a failed test.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.