jenkinsci / jenkinsci/junit-plugin

[JENKINS-25996] All Failed Tests - name ordering issue

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

Description

Ordering the Failed Tests by name doesn't seem to be fully working : there's always one test case that is not ordered (at the top when alphabetically ordered, at the bottom otherwise). Test case name differs from one build to another (see attached screenshots).

Please note all the test cases have a unique name.

---
Originally reported by mildju, imported from: All Failed Tests - name ordering issue


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

Raw content of original issue

Ordering the Failed Tests by name doesn't seem to be fully working : there's always one test case that is not ordered (at the top when alphabetically ordered, at the bottom otherwise). Test case name differs from one build to another (see attached screenshots).

Please note all the test cases have a unique name.

environment

```
Jenkins version 1.580

junit-plugin version 1.1
```

2 attachments

- [junit-plugin_bug.JPG](https://issues.jenkins.io/secure/attachment/28138/junit-plugin_bug.JPG)
> ![junit-plugin_bug.JPG](https://issues.jenkins.io/secure/attachment/28138/junit-plugin_bug.JPG)
- [junit-plugin_bug2.JPG](https://issues.jenkins.io/secure/attachment/28139/junit-plugin_bug2.JPG)
> ![junit-plugin_bug2.JPG](https://issues.jenkins.io/secure/attachment/28139/junit-plugin_bug2.JPG)

Contributor guide

Open the contributing guide

Research direction

No source files or tests are named. Start by reproducing the failed-test name ordering with Jenkins 1.580 and junit-plugin 1.1, using the two attached screenshots for comparison. Done means uniquely named failed tests sort consistently by name in both ascending and descending order.

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.