jenkinsci / jenkinsci/junit-plugin

[JENKINS-4197] better jUnit results for specified build - history/future info

Open
#836 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

When clicked on JUnit results (build/single test) for build #XYZ Hudson reports
PASS/FAILED/IGNORED info only for "this time" = "this build". I am missing
informations about future and past for result of a tests.

  • When they firstly failed from last build where they with pass (+ link to that
    build) = history for test
  • When they firstly pass from this build (+ link to that build) = future for
    that test

Example:

Lets have test1 and test2.

Lets have builds:
#8 both failed
#9 test1 passed
#10 test1 failed
#11 test1 failed, test2 failed
#12 build aborted - compilation failure, no test runned
#13 test1 passed, test2 failed;
#14 test1 passed.

jUnit results for builds
#14

  • test1 pass
  • test2 pass

#13

  • test1 pass
  • test2 failed (first failed in #11)

#12
no results

#11

  • test1 failed (already fixed in #13, first failed in #10)
  • test2 failed (first failed in this build)

and so on...

Inspiration from Teamcity, this feature is only reason in our company for
running both Hudson (free, flexible, open source, more plugins (btw: thanks for
Selenium and Swarm), no limits like TC) and Teamcity (better reports, QA can´t
work without it - find where some test first failed in line of builds in Hudson
is hardcore work (if this info even exists because of "discard old builds function")

more at known URL
http://www.jetbrains.com/teamcity/features/code_quality.html#Test_Count


Originally reported by hanys, imported from: better jUnit results for specified build - history/future info
  • status: Open
  • priority: Major
  • component(s): junit-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 2025-11-26
Raw content of original issue

When clicked on JUnit results (build/single test) for build #XYZ Hudson reports PASS/FAILED/IGNORED info only for "this time" = "this build". I am missing informations about future and past for result of a tests.

  • When they firstly failed from last build where they with pass (+ link to that build) = history for test
  • When they firstly pass from this build (+ link to that build) = future for that test

Example:

Lets have test1 and test2.

Lets have builds: #8 both failed #9 test1 passed #10 test1 failed #11 test1 failed, test2 failed #12 build aborted - compilation failure, no test runned #13 test1 passed, test2 failed; #14 test1 passed.

jUnit results for builds #14

  • test1 pass
  • test2 pass

#13

  • test1 pass
  • test2 failed (first failed in #11)

#12 no results

#11

  • test1 failed (already fixed in #13, first failed in #10)
  • test2 failed (first failed in this build)

and so on...

Inspiration from Teamcity, this feature is only reason in our company for running both Hudson (free, flexible, open source, more plugins (btw: thanks for Selenium and Swarm), no limits like TC) and Teamcity (better reports, QA can´t work without it - find where some test first failed in line of builds in Hudson is hardcore work (if this info even exists because of "discard old builds function")

more at known URL http://www.jetbrains.com/teamcity/features/code_quality.html#Test_Count

  • environment: Platform: All, OS: All
1 attachment

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

The issue concerns the junit-plugin's JUnit results for a specified build and requests history and future links across builds. Start by tracing how build and individual test results are displayed, then compare the requested behavior with the #8–#14 example. Done means results identify the first failure, later fix, and relevant builds while handling builds with no test results.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.