jenkinsci / jenkinsci/junit-plugin
[JENKINS-31040] Group failed tests by error
- Dominant language
- Java
- Stars
- 87
- Forks
- 351
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 2
Description
Background
When we use JUnit for acceptance testing, sometimes lot of tests are failed due to the same problems. This happens especially when we integrate big changes. For example, 10 causes can make 100 tests failed. In this circumstance, we need to easily find which tests are failed by which causes. It would help us to quickly report failed tests.
Suggestion
- Group failed tests by error
- Failed tests with the same problem might have similar error message.
For example
Error
Failed Tests
Some Exception
test1
test2
test3
Some Exception2
testA
testB
---
Originally reported by
linugee, imported from: Group failed tests by error
lakshitha
Raw content of original issue
Background
When we use JUnit for acceptance testing, sometimes lot of tests are failed due to the same problems. This happens especially when we integrate big changes. For example, 10 causes can make 100 tests failed. In this circumstance, we need to easily find which tests are failed by which causes. It would help us to quickly report failed tests.
Suggestion
- Group failed tests by error
- Failed tests with the same problem might have similar error message.
For example
Error
Failed Tests
Some Exception
test1
test2
test3
Some Exception2
testA
testB
Contributor guide
Research direction
The issue names the junit-plugin and JUnit acceptance-test results but provides no files, tests, or entry points. Start by locating the code that presents failed JUnit tests and determine how similar error messages should be grouped; done means failed tests are displayed under their corresponding errors as in the example.
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
- Needs clarification
- Newbie friendliness
- 25/100