jenkinsci / jenkinsci/junit-plugin
[JENKINS-1832] Hudson uses testcase@classname instead of testsuite@name for report generation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 87
- Forks
- 351
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 2
Description
This has been already fixed once and then reverted. It would be really nice to
have it back again. I didn't dig deeply into the reason for reverting the patch,
but I hope it will be possible.
Some links:
http://www.nabble.com/difference-in-junit-publisher-and-ant-junitreport-td12265700.html#a12265700
Issue #1233
http://www.nabble.com/Test-naming-in-Hudson-1.219-tt17733573.html
Originally reported by dvrzalik, imported from: Hudson uses testcase@classname instead of testsuite@name for report generation
- assignee:
kohsuke
- status: Open
- priority: Critical
- component(s): junit-plugin
- resolution: Unresolved
- votes: 1
- watchers: 0
- imported: 2025-11-26
Raw content of original issue
This has been already fixed once and then reverted. It would be really nice to have it back again. I didn't dig deeply into the reason for reverting the patch, but I hope it will be possible.
Some links: http://www.nabble.com/difference-in-junit-publisher-and-ant-junitreport-td12265700.html#a12265700 Issue #1233 http://www.nabble.com/Test-naming-in-Hudson-1.219-tt17733573.html
- environment:
Platform: All, OS: All
4 attachments
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the junit-plugin report-generation code; no source files or tests are named in the issue. Compare the attached JUnit XML files and review Issue #1233 plus the linked discussions to understand why the earlier fix was reverted. Done means report generation uses testsuite@name rather than testcase@classname without regressing the prior behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100